>>>>Yes - Public and default variables (AKA Private) would be visible, as opposed to Local vars.
>>>>
>>>>
>>>>hth
>>>
>>>You did test it with the form, correct? In various form's methods?
>>
>>Keep in mind that PRIVATE does ***NOT*** 'create' any variable.
>>So if you want such "variables" available with some value in later methods/functions/etc you have to both declare them PRIVATE and assign values to each right away.
>
>I would put it that way:
>Private is not a declaration, as opposed to Public and Local.
>An undeclared variable is available as long as the method/procedure where it was created is in the calling stack. (IOW, in a procedure and all subprocedures called from there.
>In case of a project's "main.prg" that means it is available as long as the app is running (unless being explicitly Released)).
>
>The Private keyword is only required when you want to protect an existing undeclared variable when you create a new one with the same name in a sub-procedure.
>So "Private" is not a declaration but a kind of umbrella.
OK. But declaring the "special" PRIVATEs in main.prg and assigning the 'default' value for each can only help to signal the reader that these are special for the whole program.
>
>
>-Stefan
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only