efopen.c (about void voids)

Snoopy seifert at hammer.UUCP
Wed Oct 30 06:12:43 AEST 1985

In article <267 at frog.UUCP> john at frog.UUCP (John Woods) writes:

>Although I am sure that someone has a compiler for which the following will
>not make sense, in general the construct
>#ifndef lint
>#define void int
>allows one to have one's cake and eat it too.

What doesn't make sense is having a combination of compiler and lint
where one knows about void and the other doesn't.

(Sure it's *possible*, but WHY?)


More information about the Comp.lang.c mailing list