>Why redefine private scope to local ?

Visual FreePro defines a _caller object which is able to access data in functions on up the caller stack. Private variables are local variables in function, but they are not visible through the _caller object. This allows code executing at a given point to isolate its data from external reference.


>Param missing totally (see above, granting that LPara is cleaner) ?

I am leaning toward mapping both PARAMETERS and LPARAMETERS to a new PARAMS keyword which provides a syntax to allow a scope for all or individual parameters (as to private or local as by name or direct indication).

FUNCTION foo
PARAMS pnParam1.private, pnParam2.local

>IIRC currency is in vfp an 8byte Int only interpreted as "N,x,4" similar ? Your
>"64-bit floating point field represented as a currency (legacy)" reads wrong

The word "legacy" there refers to it being a currency as per the system settings. That's legacy mode. In the new VFRP mode, each currency column in a table created with a legacy system will have a currency type associated with it. If the table was created in VFRP mode, then it will include the currency flag to allow every field on every row to individually have its own associated currency type.

Thank you for your input.