authorplaceholder@gorgo.UUCP.UUCP (02/18/87)
Is lex known to be bletcherously buggy on xenix 3.3a1, running on an Altos
2086?
I just tried to run jive through it (several times, in fact), and what pops
out the other end has lines of input buried in it. I tried to hack the lex
output (as much as any mere human can hack lex output), and got it to
compile clean, but it wasn't functional.
I really must apologize to those of you who are reading my steady stream of
queries and complaints.
Do other folks with Altos/XENIX have a lot of problems with it? Is there some
place where I can get a list of known bugs and problems?
David Drexler
ihnp4!{nears | occrsh}!gorgo!ddrexmilo@ndmath.UUCP (02/22/87)
In my experience, Altos Xenix stinks really bad, I did a review on it for Byte awhile back...but lately I have been noticing even more problems Recently I tried to compile EMPIRE on the Altos, it ran but has many unexplanable bugs (which don't appear on a VMS compiled version). I spent a great deal of time hunting down one of the bugs and finally found that the bug was actually in the C compiler...when I removed references to register variables the code ran fine. I have also had the Altos Xenix compiler barf on many other public domain programs including Super Rogue (preprocessor died), news 2.10 (compiled but running postnews caused system crashes) and several others. All the programs mentioned above ran fine on both a SUN and a VAX. We also tried compiling some other programs on SCO Xenix V on an AT and had similar problems. Personally, I think the Xenix C compiler stinks! Commercial applications seem to work more-or-less ok but if you want to run any public domain stuff you might as well forget it. Greg Corson