Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Xenix cc bugs
Message-ID: <2362@sixhub.UUCP>
Date: 23 Nov 90 04:04:42 GMT
References: <720@iris.mincom.oz.au>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 27

In article <720@iris.mincom.oz.au> cjm@iris.mincom.oz.au (Chris Moran) writes:

| We are running with SCO Xenix 386 SysV, Rel. 2.3.2, Development system 2.3.1,
| with SLS lng244 installed.

  I don't see a lot of this anymore with the recent versions, but there
was a lot of it, and you can (as you showed) still stumble of it. My
favorite was one program which broke the parser because of nesting, just
like yours, but the break fell on a line saying:

	if (ALMODE) {

where the config.h #defined ALMODE to 1. I called SCO and the 1st level
person I talked to, on being told the ALMODE was one, suggested I could
"siplify the program by setting ALMODE to zero."

  Later one of their top people got on the line with me and gave me the
*real* answer: "that's a known bug."

  I figure that for every hour I spend on a bug I save a day by being
able to cross compile to Xenix/286 and DOS, so I use the compiler, and
have little trouble with the current versions.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me