PE> NULLZERO.C(3): Error! E1055: Unable to open 'alloc.h'

  I didn't realise alloc.h was nonstandard. Use stdlib.h.

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

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

 PE> NULLZERO.C(53): Error! E1082: Statement required after label

  I didn't know that. You'll have to add a semicolon after the first 
label too, or the compiler will think the fclose() only applies to the 
label.

 PE> NULLZERO.C(12): Warning! W301: No prototype found for 'clrscr'

  I dunno how that happened. clrscr() shouldn't be there.

 PE> NULLZERO.C(29): Warning! W301: No prototype found for 'malloc'
 PE> NULLZERO.C(54): Warning! W301: No prototype found for 'free'
 PE> Error: Compiler returned a bad status compiling 'NULLZERO.C'

  These are just alloc.h

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

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

  I think I got that wrong, too. I vaguely remember David telling me
you *have* to typcast what malloc allows, thus... (char*)malloc(16);
even though Borland seems to accept it. I'm not too sure what happens
with the overlap in memory, either. I suppose the next one just get
written on top so it doesn't matter.

Regards,
Bob
 

Regards,
Bob


  
___ Blue Wave/QWK v2.12
@EOT:

---