ANSI <--> K&R conversion utilities - COMMING SOON

[Norman Diamond]

In article <CLINE.89May29171059 at sun.soe.clarkson.edu> cline at sun.soe.clarkson.edu (Marshall Cline) writes:

> >(4) When converting from ANSI to K&R, the "automatic cast" facilities
> >    provided by the prototypes would have to be changed to "explicit casts".
> >    Ex: If "myfunct()" accepts a "long", and "i" is an "int", then the
> >    ANSI code "myfunct(i)" would have to be translated to "myfunct((long)i)"
> >    for the K&R compilers.

In article <229 at pink.ACA.MCC.COM> rfg at pink.aca.mcc.com.UUCP (Ron Guilmette) writes:

>Who wants to go backwards?

Anyone who has to use a K&R compiler, e.g. PCC.  Technically this
doesn't answer the question; this answers "Who HAS to go backwards?"
Anyway, Mr. Cline is right; the perverse transform is also useful.

--
Norman Diamond, Sony Computer Science Lab (diamond%csl.sony.co.jp at relay.cs.net)
  The above opinions are my own.   |  Why are programmers criticized for
  If they're also your opinions,   |  re-implementing the wheel, when car
  you're infringing my copyright.  |  manufacturers are praised for it?