PE> NULLZERO.C(29): Warning! W102: Type mismatch

BL> Eh? Can't I say while(1 == 1)?

You can, it was probably triggered off from something else.

BL> As I've told you earlier, I think portability is silly. You have to 
BL> recompile, so you may as well fix it at the same time. It's really no
BL> different than what happens in normal writing... you leave things out
BL> accidentally and do running rerpairs as the compiler directs.

The idea is to not need to be told, you get it right first time.

PE> line[16] = '\0';
PE> names[n] = malloc(16);

BL> I think I got that wrong, too. I vaguely remember David telling me
BL> you *have* to typcast what malloc allows, thus... (char*)malloc(16);

Not in C.  In C++ that is "true" (not sure if it's only a
warning).  BFN.  Paul. 
@EOT:

---