Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!decvax!cwruecmp!atvax!ncoast!bsa
From: bsa@ncoast.UUCP (Brandon Allbery)
Newsgroups: net.lang.c
Subject: Re: C needs BCD (ANSI People: Please Listen)
Message-ID: <436@ncoast.UUCP>
Date: Thu, 25-Oct-84 15:14:06 EST
Article-I.D.: ncoast.436
Posted: Thu Oct 25 15:14:06 1984
Date-Received: Sun, 28-Oct-84 07:07:23 EST
References: <218@x.UUCP> <>
Reply-To: bsa@ncoast.UUCP (Brandon Allbery)
Organization: North Coast XENIX, Cleveland
Lines: 19
Summary: Xenix-68K (1.03.02) has it... with MS's usual documentation

Strange how net subjects hit you in unexpected places.  Just after reading
the request for C BCD, I was trying to compile a program which had somehow
become garbled.  One set of error messages it produced was:

... newline in BCD constant
... BCD constant too long
... gcos BCD constant illegal

The source code?

				offset -=`BLKSIZE;

(I *said* the code was garbled.)  I get the feeling MS foisted yet *another*
undocumented feature on us.  The question is, is this one like the IOCTL
calls for multiplex files and for the Berkeley `NTTY' discipline (i.e.
they're there but don't do a (@) thing)?  And why `gcos'???  This is
supposed to be *Microsoft* :-)

--bsa