Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Emulating Visual Foxpro Command Window
Message
From
03/08/2000 10:05:47
 
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
00399066
Message ID:
00400337
Views:
14
>Thanks for the heads up, Ed. I knew it...
>
>Anyway, it's sill not a Command Window Emulator. I was thinking about this problem at home and it seems to me, that if we want to emulate Command Window, e.g. pressing Enter, execute the command, it should declare variables as public, e.g. :
>User types in "Command Window Emulator"
> a=5 and presses Enter.
>
>Our emulator makes it as 2 lines of code:
>Public a
>&lcLine
>

Creating all variables as public is a good way to smash things up in a hurry. I'd suggesat downloading one of the numerous classes that already implement a Command Window emulator; writing a parser that works properly, enforces scoping properly, and doesn't smash up is non-trivial.

As far as assigning values, there are lots of other ways; SCATTER, ADIR(), ACOPY() SAVE TO/RESTORE FROM, PUBLIC, LOCAL - the list goes on and on.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform