🚀 go-pugleaf

Please note - just passing a message from Johann Ruegg, Sozobon Ltd.,
ncar!dunike!onecom!wldrdg!hans.  Please reply directly to him, or
other Sozobon guys (unless a dire emergency will arise).

   Michal (...{ncc,alberta}!myrias!mj)

>>>>>>>>>>>>>>>>>>>> (Hans message follows) >>>>>>>>>>>>>>>>>

The next release of Sozobon C is coming out soon.  This is the list
of currently known compiler bugs (when the compiler is compiled with
itself - other problems appear when the tools are re-compiled).  If
you know of others, please send them to me at

	ncar!dunike!onecom!wldrdg!hans

Please include a sample of the code that fails.

All of these will be fixed in the next release.  (Its amazing that
anything worked with the current release isn't it :->).

1) '<=' or '>=' appearing with constants on BOTH sides actually
do '>=' and '<=' instead

2) '<' '>' '<=' or '>=' appearing with a constant on the LEFT act as if
   '<=' '>=' '<' or '>' had been specified instead

3) unsigned char expressions are passed to functions as signed char

4) complex expressions involving '!' like "b = !(b==0)" may fail

5) float comparisons with both values negative and nearly equal may fail

6) structures which contain only an odd number of 'char' fields dont work.

7) funny structure practices like "subr(s=t)" where s and t are structures
  dont work.

8) 'case' or 'default' outside any 'switch' bombs the compiler

9) the assembler (jas) doesn't handle bit ops properly (btst, bchg, ...)

		- Johann Ruegg
		  Sozobon Ltd.
		  ncar!dunike!onecom!wldrdg!hans