Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
To iif or not to iif = .t.
Message
From
01/06/2001 15:25:39
 
 
To
01/06/2001 14:42:24
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00513276
Message ID:
00513993
Views:
15
SNIP
>
>I think George Tasker hit the nail on the head in an earlier message: that he considers them the equivalent of GOTO in Basic - with all the problems that causes.
>
C'mon Al, it's nothing of the sort.

Goto can end up anywhere while LOOP goes to only one place and EXIT goes *only* to the place that you are going to go to anyways. There's a HUGE difference.
I'm not arguing against your personal standard, just the justification you (and George) use for this particular one.

Commenting on another thread about PRIVATEs, etc. the good old reliable "nasty unexpected and impossible to find bugs" and variations thereof have been trotted out to rail against PUBLIC in 'modern VFP code'.
Yes, I can see where this ***could*** be a problem during debugging *IF* one is debugging several components at the same time. But I think there are other more serious issues if one is debugging that way. And it is true that PUBLICs *can* lead to surprises in even basic code when one is debugging. But having PRIVATEs in MAIN leads to just about all the same issues, so this "publics are blasphemous' is way overworked in my humble opinion.

Regards,

JimN
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform