Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Use of macro substitution vs. string valued variables
Message
From
22/07/1999 15:49:48
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
 
 
To
22/07/1999 13:30:24
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00244254
Message ID:
00244947
Views:
18
>>One useful thing for the macros I found was for calling a procedure whose name is in a table, or calculated somehow - like when I calculated interest using several methods, and calling calc01, calc02, calc03 routines, and, you may guess, the table contained "01", "03" and such in the UseMethod field. Then I calculated the factor like this:
>>
>>lcMeth=table.UseMethod
>>lnCoeff=calc&lcMeth()

>You still don't need macros to do this- you can use EVAL instead.
>
>lcMeth= "calc." + ALLTRIM(table.UseMethod) + "()"
>>lnCoeff=EVAL(lcMeth)
>
>Faster, and IMHO, better.

Agreed. Nowadays I also use Eval() wherever possible - though there are some soft spots left for the &.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform