>>Too logical not to be true... A-T as an organization became real jerks when they started to lose their edge... FWIW: I really hate the SYS() functions because there is no way to know what any given one does without checking HELP or some other reference first. At least an 'english-like'/'human-readable' name would be a good start and hopefully help quickly determine a better approach/command to accomplish a task...
>
>I just thought of this...but we don't need MS to fix this. We can do it now using the preprocessor.
>
>#DEFINE MyFunction() SYS(0)

No go, Craig. You can't #define function names, AFAIK. I've tried your example, and tried

#define myfunc(a,b) abs(a+b)
?myfunc(1,2)

But it displays several very imaginative error messages, depending on the way you try to fool it - and still doesn't go. Clipper had something like this, and though it would make for more unreadable code and a more complicated compiler, I'd still like to have it.

You can still

#define ConfigFile sys(2019)
#define PushText Fwrite(fHandle,

and then do

modi comm ConfigFile
fHandle=fcreate("whatever.txt")
PushText "Hello, world")

...and greatly reduce the typing efforts and readability :)