scs@adam.mit.edu (Steve Summit) (02/07/91)
In article <1991Feb6.070307.1970@athena.mit.edu>, I wrote that
ANSI-compatible versions of lint were available from two
companies: Gimpel Software and Mortice Kern Systems. I know
there are two companies out there with lints (someone posted
information about both of them recently), but MKS isn't one of
them. If the person who posted the succinct summary of
commercial lint availability would _mail_ me the correct
information, I'd appreciate it. In the meantime, don't pester
Mortice Kern about lint -- evidently it's a question they get all
the time already.
Steve Summit
scs@adam.mit.eduandy@mks.com (Andy Toy) (02/09/91)
In article <1991Feb7.034007.20606@athena.mit.edu> scs@adam.mit.edu writes: >>ANSI-compatible versions of lint were available from two >>companies: Gimpel Software and Mortice Kern Systems. >I know there are two companies out there with lints (someone posted >information about both of them recently), but MKS isn't one of >them. [...] In the meantime, don't pester Mortice Kern about lint -- >evidently it's a question they get all the time already. I can definitely verify that MKS does not have lint. However, it is a good idea for an MKS product so I have suggested it to the product development department. -- Andy Toy <andy@mks.com> UUCP: ...!uunet!watmath!mks!andy Technical Support <support@mks.com> Phone: +1-519-884-2270 Mortice Kern Systems Inc. <inquiry@mks.com> Phone: +1-519-884-2251 35 King Street North, Waterloo, Ontario N2J 2W9, CANADA Fax: +1-519-884-8861
scs@adam.mit.edu (Steve Summit) (05/03/91)
There's a small typo in the FAQ list posted yesterday.
In question 62, the sentence
You will have to give the structure a tag ("struct node"),
and declare the "next" field as "struct node next;".
should of course read "struct node *next;".
Thanks to Chris Torek for pointing this out.
Steve Summit
scs@adam.mit.edu