Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lasspvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!lasspvax!jtp
From: jtp@lasspvax.UUCP (Garry Wiegand)
Newsgroups: net.lang.c,net.lang.pascal
Subject: Re: Need Pascal to C translator
Message-ID: <701@lasspvax.UUCP>
Date: Wed, 20-Nov-85 14:51:49 EST
Article-I.D.: lasspvax.701
Posted: Wed Nov 20 14:51:49 1985
Date-Received: Sat, 23-Nov-85 03:30:23 EST
Reply-To: garry%geology@cu-arpa.cornell.edu.arpa
Distribution: net
Organization: Cornell Engineering && Flying Moose Graphics
Lines: 21
Xref: watmath net.lang.c:7128 net.lang.pascal:382

I have a more unusual need: PL/1 -> C!  We are succumbing to popular
opinion and converting about 25K lines of VMS PL/1, and it's gonna be a pain.

I already with through the exercise of changing a 10,000 line package,
and it took months before all the bugs were out! &'s and *'s in
procedure calls and parameters turned out to be the major source
of lurking problems. 

We did not have a copy of Lint then --- it would have been *some* help, 
but it seems to be hard to get it to check usage between separately
compiled unit. The only way I can think of to get it to check for consistent
by reference/by value parameter usage in such cases is to concatenate 
all 25K lines into one huge file, start the check, and come back tomorrow.

Needless to say, since it will take many many such cycles, is there a
better way to apply Lint to the problem?

(PS - PL/1 to C translators cheerfully accepted!)

Garry Wiegand
garry%geology@cu-arpa.cs.cornell.edu  (arpa)