Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uunet!cbmvax!cbmehq!cbmger!kbsaar!fjrei From: fjrei@kbsaar.UUCP (Franz-Josef Reichert) Newsgroups: comp.sys.amiga.programmer Subject: Re: Dumb windows from SAS/C programs on Workbench Message-ID: Date: 15 May 91 19:05:00 GMT References: <1991May14.164909.19186@NCoast.ORG> Organization: Private Amiga Site Lines: 30 In article <1991May14.164909.19186@NCoast.ORG> davewt@NCoast.ORG (David Wright) writes: > > Can anyone tell me if there is a simple way to get rid of the stupid >windows that SAS/C opens up by default when you start a program from the >WorkBench? I can obviously diddle with c.a and umain.c to eliminate this, >but it seems like there MUST be an easier way to do this. > I am using the "tinymain" option, in both my SASCOPTS file, and >in the Blink ".lnk" file, and do not make any use of printf/fprintf, and >so have no use for a default "stdin", "stdout", or "stderr". So you can rename your main() function entry as '_main()'. That's simpliest, as long as you aren't doing any terminal- or file-I/O. Be aware, this also disables argument passing via the command line. > On a related note, what do you have to do to kill the CTRL-C trapping >their startup code puts in by default. I have my own trapper which worked >fine in Draco programs, but SAS/C seems to grab the signals before I have >a chance to see them, and is dumping my programs without giving me a chance to >clean up, close files, etc. See your manual P. L-156 to learn more about how to set the break trap to your favourite function entry. > Dave -- Best regards, Franz-Josef Reichert VOICE: +49 6805 7417 Kuchlingerstrasse 13 UUCP: ...uunet!cbmvax!cbmehq!cbmger!kbsaar!fjrei D-6601 Kleinblittersdorf GERMANY