Message-ID: <6745@brl-tgr.ARPA>
Date: Sat, 22-Dec-84 16:11:58 EST
Article-I.D.: brl-tgr.6745
Posted: Sat Dec 22 16:11:58 1984
Date-Received: Tue, 25-Dec-84 02:48:39 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 23

Some early versions of BDS C v1.5 did indeed use RST 6, but as soon as I
realized this was wiping out console I/O vectors left and right I stopped
distributing it that way. The usage of a RST vector is solely connected with
the CDB (C symbolic debugger) mechanism...when you do not intend to use  CDB
on a program, there is no reason for any RST locations to be clobbered. The
reason I originally had the run-time package write into RST 6 was for the case
where someone creates a COM file intended for use under CDB (and thus filled
with RST 6 calls), then tries to run it standalone. It would bomb if CDB were
not there to intercept the RST 6 calls. So, I had the run-time package put
a little "no-op" subroutine at location 30h. Bad idea.

The way it works NOW is: the mechanism for writing the dummy subroutine is
still there, but it is not enabled until you go in and change some EQU's and
reassemble the run-time package. Apologies to those of you who have wasted
time puzzling over bombing BDS C programs because of this.

One more note: the phenomena where BDS C-coded utilities refuse to put out
characters until the keyboard is hit can be fixed by recompiling the programs
under v1.5. Eariler versions of the library did indeed do the wrong thing
when looking at the return value from "check consle status". This problem
is likely to keep popping up and biting people until the binary versions of
programs like SQ-USQ are updated with more current libraries.
	-leor

Message-ID: <10000019@acf4.UUCP>
Date: Sat, 22-Dec-84 19:02:00 EST
Article-I.D.: acf4.10000019
Posted: Sat Dec 22 19:02:00 1984
Date-Received: Tue, 25-Dec-84 03:12:36 EST
References: <6745@Mit-Mc.UUCP>
Organization: New York University
Lines: 16
Nf-ID: #R:Mit-Mc:-674500:acf4:10000019:000:598
Nf-From: acf4!greenber    Dec 22 19:02:00 1984

<>

While we have you on the line.....do you think that you could
put the infamous "printf" problem in your documentation.  Took me
about two days to figure out what was going on (For those who don't
know: BDS C can handle lines of only MAXLINE in length.  Printf goes
out to lunch, even with 'printf("%20.20s", string);' if string is longer
than MAXLINE).


For those who haven't experienced yet --- I'll bet you a dollar that you
do. But you only experience it once!!!


------------------------------------------------------
Ross M. Greenberg  @ NYU   ---->  allegra!cmcl2!acf4!greenber  <----