CompuServe Messages

I did get my 5.10 upgrade… and I'll probably never use the new Workbench Interface stuff. One thing I noticed right outta the gate was that some of my Make files broke when it was time to link…. I expand a reasonably long list of objects (maybe 15) on my BLINK line, and it crashed on the long line! When doing the BLINK from the command line, I got an error, but no crash. I now have to write a "WITH" file, an extra step I detest. Another caveat is that the pure bit isn't set in BLINK… as someone who likes to make these things resident, that was discouraging: a definite step backwards. On the other hand, I tried making it resident and haven't had any problems. Some of the include files are mis-named. wb_proto.h is referenced from another include file as "workbench_proto.h" (or something like that… there are a few wb -> workbench conversions that need to be done). Doesn't look particularly professional. Normally, if I ran into problems like these, I'd be on the line to tech support, an set them straight…. but not on MY nickle at $2.00 a minute. They'll have to find out that at least some small subset of tech-support calls are not for our health, but for theirs! I don't mean to be negative. The code generated works… which is an improvement significance over some Lattice releases (where major crashes were associated with, say, the transcendental functions, or casting a float to a double on a return!). BLINK seems faster, and it's real nice having the 2.0 includes and lib. Now how about SAS really doing the right thing, and updating that antiquated C++ preprocessor?