Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: disadvantages of using old parameter syntax? Date: Sat, 12 Sep 2015 14:25:04 -0700 Organization: None to speak of Lines: 30 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="19064"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/YU/e0pOvcUNPN0fs1Ww7q" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:C8h+9O+fTAZjRrnW5H7vrkY5zHk= sha1:HA86xKMc1DFtpTwohR3x31j207A= Xref: csiph.com comp.lang.c:70386 Anonymous Shadow writes: > I think I should also mention that in the zlib source distribution, > there is a perl script that /attempts/ to "transform K&R C function > definitions into ANSI equivalent". It is called zlib2ansi, and seems > to work quite well, with the few small programs that I have tried with > it. It does have one problem (which is difficult to avoid). It translates this: int func(arg) short arg; { } to this: int func( short arg) { } which is not equivalent. For the purposes for which it's used that's probably not worth fixing. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"