🚀 go-pugleaf

In article <692@ttidca.TTI.COM> woodside@ttidcb.UUCP (George Woodside) writes:
>Known bugs - there is a glitch in the assembler which causes the value of
>generated long constants to have their high order byte zeroed (ie. 0x87654321L
>yields 0x00654321L in the object. Printf will still not write any output until
>it gets a line feed (this is not a bug as far as MW is concerned, but a design
>"feature").


	Firstly, many kudos to George Woodside for his excellent TURTLE
hard disk backup program. It is absolutely the best backup utility out
there, commercial or otherwise. Thanks.

	Just to add to to the bugs list above, we've come across the
following:

	- Some of the Bit testing type constructs generate a cryptic
internal compiler error message. For instance

	typedef struct {
		char *name;
		int flags;
		....
	} AType;
	
	#define THISFLAG 0x0020
	Atype *x;
	.....
	
	if(x->flags & THISFLAG) ...
		^^^^^^
	  On this line it will generate an internal compiler error and
	 will display a hex number.
	This was reported to MWC and they said it would be fixed.

	- the rindex() library routine does not return a NULL is a
	NULL string is passed to it. pm@case spent many hours tracking down
	a bug caused by this.

	char *s, *t;
	extern char *rindex();

	s = "";
	t = rindex(s,'<any chararacter>');

	returns s, and not (char *)NULL;

	
The printf bug you describe above is not a bug, as standard i/o streams
(except perhaps stderr, depending on who you talk to) are buffered.
These buffers are flushed only when they are full, or when and end
of line is written, or when they are closed. If you need to flush a
stream, use the fflush() call.

Now i wish MW would lift the silly 32k limits on the static data structures.

	Other than the minor inconveniences listed above, MW works great
for me.
-- 
usenet: {decvax,cbatt,cbosgd,sun}!cwruecmp!bammi	jwahar r. bammi
csnet:       bammi@case
arpa:        bammi%case@csnet-relay
compuServe:  71515,155