Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!POSTGRES.BERKELEY.EDU!dillon
From: dillon@POSTGRES.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: ST PROGRAMMING
Message-ID: <8811300419.AA08982@postgres.Berkeley.EDU>
Date: 30 Nov 88 04:19:49 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Lines: 53


	Before Pete comes on with a huge flame against you, because in this
case he would be completely justified, I would like to give you a medium
flame (to prepare you for Pete's flame which will no doubt occur the moment
he reads the message, eh? (-:).

	What you are saying below in your response is, essentially, that if a 
person wants to disable break he cannot perform certain useful system calls
and library functions on the ST because they catch ^C and kill the program.
You say that this is not necessarily a bad thing.

	(1) ?!?!@ Hogwash.  That makes no sense at all.  And, since you are 
	    so fond of quoting UNIX, I would like to point out that it is
	    a very simple matter to disable INTR (^C) .. a single line of
	    C in fact on UNIX systems.

	(2) I was under the impression that you could disable ^C for these
	    functions on the Atari.  Anybody know for sure?

	(3) I mean, your response *really* makes no sense at all.. just
	    read it over again!  Give me a break!

					-Matt

From: crewman@bucsb.UUCP -- JJS Writes:
:In article <3028@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
:>In article <36@raider.MFEE.TN.US>, dana.holt@raider.MFEE.TN.US seems to
:>>      This reply is directed toward the cooment you made about the Atari ST 
:>> inability to survive a ^C in any of the built-in input functions.
:>
:>No, I said that there is no way of surviving ^C using the standard I/O
:>functions. That is, the UNIX-style file routines directed at the console
:>device.
:>
:
:Is that supposed to be undesirable?  After all, as you say yourself, these are
:UNIX-style routines which act just like UNIX does in case of ^C.  These 
:routines are there for the console device - a text-based shell, not some
:fancy graphics-based input filter.  It's not that there is no way to survive
:^C; the ^C exit was put in deliberately to resemble UNIX!
:
:>
:>Yes, but as soon as you call printf() you're a dead puppy.
:>
:
:Don't use printf().  Use sprintf() followed by one of the ROM string output
:routines.  Again, printf() works just like it should -- just like in UNIX.

	One last comment:  Don't use printf() ???? THAT IS YOUR SOLUTION??!
Great, Just what I needed to hear.  What?  Oh yah, I was going to keep this
a medium flame ...

						-Matt