Information générale
Catégorie:
VFP Compiler for .NET
Hi Hugo:
You are absolutely right. () should be mapped to LPARAMETERS, our docs are wrong about that. We fixed that in our compiler and should appear soon in the ONLINE version.
With this change, (parameter_declaration) should behave as if you have declared them with LPARAMETERS parameter_declaration and that is the VFP way.
Thanks.
>Samuel,
>
>Looking into your web I found you say (bold mine):
>
>"For parameters declaring we choose this convention:
>
> * Use LPARAMETERS instead of PARAMETERS to be sure all the parameters are local and to avoid variable name clash.
> * Prefix every parameter name with the t character, i.e. tcParameterName for a parameter containing a character value.
> * Because the syntax PROCEDURE (aParam, bParam) is mapped to PARAMETERS, try to avoid this syntax. The compiler handles fine that syntax but we don't encourage you to use it."
>
>Why not making it so it is compatible with VFP?, that is, parameters declared that way are local, not private. In my case I always like to avoid using LPARAMETERS, I like the use of (Parameter) better, but if I ever choose to use your compiler, I might encounter some problems and will need to change lots of code
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement