This is re:-A-Few-Questions... in view mode; [Up]
Date: Sun 03-Jul-1989 18:50:28 From: Unknown Subject: re: A Few Questions... In article <10374@polya.Stanford.EDU> Ali T. Ozer writes: >In article <15094@pasteur.Berkeley.EDU> dean@xcssun.Berkeley.EDU () writes: >>7) Why did lint go away ? >With an ANSI compiler, you probably won't need it. If you miss 'lint' as an entity, you can always do something like: alias lint "cc -Wall -S -o /dev/null" and then 'lint program.c' prints the warning messages but produces no binary. Of course, to redirect output to a file you'll need to redirect stderr, eg. lint program.c >& program.lint - Christopher ------- >From: woo@pioneer.arc.nasa.gov (Alex Woo)
Date: Sun 05-Jul-1989 16:44:11 From: Unknown Subject: Re: re: A Few Questions... > lint program.c >& program.lint If I am not mistaken, lint did a lot more than produce only a few messages for one file. It could for example check the consistency of a number of source files, as well as indicate if, for example, printf format arguments were properly specified for what followed. (at least in some versions). I don't think -Wall can do all of it. /ivo >From: jacob@gore.com (Jacob Gore)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.