🚀 go-pugleaf

In article <2857@husc6.harvard.edu> ddl@husc6.harvard.edu (Dan Lanciani) writes:
| In article <3697@csccat.UUCP>, jack@csccat.UUCP (Jack Hudler) writes:
| | In article <1838@bnlux0.bnl.gov> cpa@bnlux0.bnl.gov (Chris Armstrong) writes:
| | >

[Stuff on accidently overwriting your own files deleted]

| 
| | >I've found my first problem with 6.0 (apart from NULL no longer being NULL,

Well, let me Quote a little from ANSI C X3J11 Section 4.1.5 "... The macros are
NULL, which expands to an implementation defined null pointer constant..."
                                                 ^^^^^^^^^^^^^^^^^^^^^
What does this mean?  It means null isn't defined as

#define NULL    0        or
#define NULL    0L       but rather something like
#define NULL    ((void*)0)

| | >and zillions of long/short mismatch warnings being produced by char/int
| | >conversions for the first time). 
| | 
| | Last time I looks a char was 1 byte and a short(int in your case) was 
| | 2 bytes. 

This is exactly it, you basically have one of two choices to eliminate the
error messages.

1.(easiest) Reduce the warning level to level 2 or level 1
2.(hardest) Apply the necessary cast to the assignment

	int i;
	char c;

	i=65;
	c = (char)i;


Jim Sather
sather@blake.acs.washington.edu