Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why define constants
Message
From
30/10/2006 11:00:10
 
 
To
30/10/2006 10:56:47
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01164235
Message ID:
01165522
Views:
15
>>>>>>>And intellisense can tell you what 16 stands for.
>>>>>>
>>>>>>And Intellisense just jumps off the the printed page!
>>>>>
>>>>>What printed page?
>>>>
>>>>The point I'm making is that, OK, Intellisense helps you out but if the prog is printed then it can't.
>>>
>>>You are PRINTING CODE?
>>
>>Besides, I've just realised, you all talk of Intellisense obviating the need for define constants, and I said "what about reading the printed code?". Well, Intellisense DOES help out when typing (tho I find it a PITA sometimes when the bubble obscures what I'm typing) but, once the code is written, in VFP 7 at any road, it doesn't come back again with mouse hover of click when you're READING the code.
>
>It does, in VFP9, in the debugger.

So it does in VFP 7. But one doesn't always read code in the debugger, whilst the prog is running. However, having sid that, in VFP7 it tooltips up values of variables and table fields but not constants, I think. Maybe in 9 it does them too?

>
>In printed code, well, you'd just have to print the .h files as well :).

Ya boo sucks!
- Whoever said that women are the weaker sex never tried to wrest the bedclothes off one in the middle of the night
- Worry is the interest you pay, in advance, for a loan that you may never need to take out.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform