To:    Clipper programmers forced to work in FoxPro

From:  \\jjFlash

AKA:   John Forsberg

Mail Addresses:
        INTERNET:   john.forsberg@merisel.com
        COMPUSERVE: CCMAIL: John Forsberg AT MERISEL-MIA
                (or respond to CompuServe ID)  [slower]

Subject:  #define differences (2 xBase dialects)

Text:
        At heart I am a Clipper programmer, but am trapped in a FoxPro
world at the office.  Within my Clipper programming environment, I am
accustomed to the pre-processor handling #define's without regards to
where the defined constant is found.  Recently I decided to use #define's
in FoxPro rather than wasting memory with variables (no scoping in FP).
        It would appear that using #define in FoxPro does not function as
a Clipper programmer would assume.  Pleae take my advice; do not waste 
your time trying to use FoxPro #defines. Instead use private variables.
If you embed #define constants withing array tests, FoxPro fails horribly!
The debugging time required in FoxPro is not worth the effort.  Run the 
test programs and view the limitations imposed upon you.  Privates work.
#defines do not.  Play with this one.
        I have included in the ZIP the ClpTest Program, Make and .EXE files
to prove to you that #define is viable.  I have also included the FoxPro
equivalents: FoxTest1 (doesn't work due to #define) and FoxTest2 (does
work due to private vs. #define).  Run the programs.  Check the code.

CLIPPER WINS AGAIN!!

\\jj

