ac> Has anyone experienced the sort of compiler behaviour Vince mentions?  eg.

ac>   char *dest, *srce;
ac>   strcpy(dest, srce);

ac> gives a warning but

ac>   char *dest, *srce;
ac>   (void) strcpy(dest, srce);

ac> does not ... ?

I think so, but not recently.  In my experience, lint, microsoft c
and cset/2 produce the most ridiculous errors known to man.

Borland C++ 3.1 for DOS produces the best by far.  BFN.  Paul.
@EOT:

---