Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!rphroy!cfctech!teemc!sycom!ro-chp!chopps From: chopps@ro-chp.UUCP (Chris Hopps) Newsgroups: comp.sys.amiga.programmer Subject: Re: Dumb windows from SAS/C programs on Workbench Message-ID: Date: 21 May 91 07:30:13 GMT References: <1991May17.022136.1539@NCoast.ORG> <1991May20.020743.14630@NCoast.ORG> Organization: CHS Lines: 49 In article <1991May20.020743.14630@NCoast.ORG> davewt@NCoast.ORG (David Wright) writes: >In article chopps@ro-chp.UUCP (Chris Hopps) writes: >>Ah but then what about being able to handle ansi code from workbench(ie. >>people to lazy to add WB Message handler...) under 1.3 some of this stuff >>would crash the system if there were no STDIN/OUT. Under 2.0 there is a nice > The only problem with this is that the window that SAS/C opens is very >small, and most certainly not large enough to display and "real" text, enough to alert you to the problem... >maybe only 2 or 3 very short lines. Basically, it's useless. It would have been >better for them to write up a function that would "throw away" the output >without a system crash than open a window that people can't change easily. I disagree, when debuging, I don't throw all that much info into that little window, just enough to find the problem. If it is too small, I re-size it. To have a window that is very large would be in the way, and to not have a window would take a nice debuging thing out. >>icon that will bring up a cli line and then open a console so that these very >>same programs can be run under 2.0. But under 1.3 the window was needed, I > Actually, under 2.0 you have to ASK for that command line window >by explicitly running the program as if it were from the CLI, which is NOT >the same as running from the WorkBench. So this is not "fixed" even now, which >is good, since there is nothing to be "fixed" at all. The operating system >works the way it should. but it DOES allow them to be run from the workbench, this is not a fix, but an enhancement. >>someone who goes out of there way to handle WB messages, and handle IO >>correctly, won't mind prepending an underscore to there main() to >>disable such a "feature". > Actually, that is NOT the best way to do it. When you declare >"_main" you will be giving up most of the SAS/C startup/shutdown features I haven't tried the umain.c stuff, it may be better. If I remember though the question was what is an easy way to get rid of the "Dumb windows from SAS/C programs on Workbench" _main is an easy way. > > > Dave Chris... -- ------------------------ The Royal Oak Chophouse Chris Hopps Royal Oak, Michigan ....umich!wsu-cs!ro-chp!chopps cs.wayne.edu!ro-chp!chopps