evtracy@sdrc.UUCP (Tracy Schuhwerk) (08/29/90)
Has anyone else run into the SAS/C 5.10 bug in the workbench prototypes
yet? Try using the proto/all include and you'll find that they put
"workbench" instead of "wb" in one of the include lines in this file.
I have also heard of another simple bug with a macro missing a closing
parenthesis (just talked to one of my programming cohorts and he mentioned
this one... more detail in another message). Both of the problems are
simple to fix. All in all, thumbs up on the 5.10 upgrade! Well worth
the minimal fee!
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________ / / / | uunet!sdrc!evtracy
/ (___ _ /_ /_ _ __ /_/ | evtracy@SDRC.UU.NET
/ . _____)__(__/ /__/_/_/ /__/_/_/__(/__/ (__/ \ +---------------------
Structural Dynamics Research Corporation (SDRC) - Milford, Ohio
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=ragg0270@uxa.cso.uiuc.edu (Richard Alan Gerber) (08/31/90)
evtracy@sdrc.UUCP (Tracy Schuhwerk) writes: > Has anyone else run into the SAS/C 5.10 bug in the workbench prototypes > yet? Try using the proto/all include and you'll find that they put > "workbench" instead of "wb" in one of the include lines in this file. > I have also heard of another simple bug with a macro missing a closing > parenthesis (just talked to one of my programming cohorts and he mentioned > this one... more detail in another message). Both of the problems are > simple to fix. All in all, thumbs up on the 5.10 upgrade! Well worth > the minimal fee! > I have found these, which appear to me to be bugs: 1. Maybe not really a bug, but if you want to use Workbench, you can't simply put loadwb as the last line in the startup-sequence supplied with the SAS disks. If you do, and then double click on the build utility, the message "Unknown command LC" appears. The problem is that the "assigns" and "paths" are done in a file startupII and that file is only accessed by the newshell that is opened during the startup sequence. If you "loadwb" from this new shell you are OK, however. 2. When using the Options utility from the workbench, checking "No linking in LSE" on the third screen also selects "No stdio" on the first screen. This one really caused me some headaches until I figured out what was going on. It also works the other way around. 3. When using LSE I hit one of the key combinations having to do with AREXX (without AREXX running) and my machine crashed. Also be aware that the default when using Options and Build is for "No floating point". If you try to using floating point when this is selected, wierd things happen. I like using Build, but one irritating thing is this: If you simply drag the drawer containing your work (source code, object files, etc.) to the RAM: disk to work (as I do), sometimes the foo.c file gets copied after the foo.o file so Build thinks that it needs to recompile foo.c when it really doesn't. For those of you haven't used this feature, Build checks the current directory and compiles all *.c files that are newer than any corresponding *.o files. It then links all *.o files together to produce an executable. It creates an icon for the executable. If you click on this icon to run the program, a window for stdio (printf's etc.) automatically opens on the workbench. Very nice! Richard