Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
The color of comments in your code window
Message
From
19/08/2009 12:56:00
 
 
To
19/08/2009 10:50:07
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01418690
Message ID:
01419031
Views:
49
Unfortunately I'm stuck in VFP6 at the moment, so no Intellisense, so yes, I run Beautify and it does expand keywords. Actually I never got into the habit of shortening 'Replace' - really can't tell you why

>>I put a blank line after sections of code - helps me keep them separate in my mind - and after years of typing other peoples' term papers, I can't type a comma without a space. I just can't and you can't make me, so THERE!
>>
>>But, still being a lazy typist, I'll use the first 4 letters of a command, then either let Intellisense fill it in (if it's there) or run Beautify and let it expand the command.
>
>Habit is a wild beast. I'm beautifying my code after every dozen lines, as a matter of habit, it's like an itch. But it's been nearly 20 years since I last allowed it to expand keywords (back then when it was called Snap! and written in who knows which version of Pascal or something). Because of a bug which would expand REPL into Replicate instead of Replace, i.e. it didn't check whether it was a command or a function, because it didn't use the same lookups as the interpreter did. And I never checked whether they fixed it.
>
>Wait, you must be using intellisense. Beutify doesn't expand kewords, documenting wizard does. And running that is tiresome, actually harder than typing full commands :).
"You don't manage people. You manage things - people you lead" Adm. Grace Hopper
Pflugerville, between a Rock and a Weird Place
Previous
Reply
Map
View

Click here to load this message in the networking platform