Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Visual FreePro & VXB++ design debugging
Message
 
 
À
10/09/2013 17:42:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
01582710
Message ID:
01582850
Vues:
49
FWIW I prefer Local to Private because you don't have to worry about name conflicts in called methods. I screw up enough things on my own without scattering land mines around.

>Why redefine private scope to local ?
>Param missing totally (see above, granting that LPara is cleaner) ?
>TPublic: Interesting - but not sure if something along a modul concept addition (see Python imports vs. JS ugliness) might not be more helpful to programmers, even if multicore CPU will need more threads in the future
>
>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
>I am partial to tinyInt [0..2**8-1] and SmallInt[0..2**16-1] as field types without casting c(1), C(2) types, complementing your u8 and u16
>Have not made my mind up on UTC timestamps
>
>from dot functions [is]accessed and [is]changed something I have sometimes REALLY wanted in wierd debug situations and logging needs.
>But "shipping is a feature" and "just because it fills some orthogonal matrix" (my thought on many items in other links) is no reason to implement from start.
>Danger of bloating by adding features only seldom needed (unless runtime speed optimizations made possible by them)
>One thing missing from my POV: marking functions as "inline", eliminating vfp overhead for parameter passing - which might bite with some of you event ideas
>
>
>
>>I would like to welcome people to go to these links and comment here on any items found.
>>I will answer questions, but otherwise remain silent.
>>I'm just looking for other user input and will not respond.
>>
>>If you're not interested, please disregard this post.
>>
>>Thank you in advance for your assistance.
>>
>>-----
>>VXB++ (Visual FreePro's new Xbase language extension):
>>http://tinyurl.com/vxbpp
>>
>>Changes between Visual FoxPro and Visual FreePro in various components:
>>http://tinyurl.com/vfrp-changes
>>
>>Variable types supported (will be extended over time):
>>http://tinyurl.com/vxbpp-variable-types
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform