Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Any known issues with PARAMETERS()?
Message
From
30/06/2000 13:47:18
 
 
To
30/06/2000 13:23:18
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00386643
Message ID:
00387211
Views:
15
Thanks, Isacc.

I just punted on the whole issue and changed my code around. Wasn't worth the weirdness. :-)

>FWIW here's whats in the Hackers Guide ...
>
>PARAMETERS(), the FoxPro version, tells you how many parameters were passed in the last function or procedure call. PCOUNT(), supposedly added only for dBASE compatibility and not even listed in the Help index before VFP 5, tells you how many parameters were passed to the routine you're now in. This time, we think dBASE got it right.
>
>Using PARAMETERS() has always been a tricky thing. You have to be sure to grab the value as soon as you enter the routine and hope that no ON KEY LABEL or other interrupt occurs that could change the value before you get it.
>
>PCOUNT(), on the other hand, gets that part right every time. We recommend you stick with PCOUNT() and avoid PARAMETERS().
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Previous
Reply
Map
View

Click here to load this message in the networking platform