jss@sjuvax.UUCP (J. Shapiro) (11/18/85)
I am sure that this question has come up before, but I am afraid I must pose it again. I find, that for reasons of portability and code simplification I must convert a large program (> 7K lines) from Pascal into C. Needless to say, I would greatly like to automate as much as possible of the process. Unfortunately, the pascal is nonstandard. I am converting a VMS pascal program, which means that if your converter does not already do VMS pascal I will have to extend it to handle the VMS extensions. If anyone out there knows of such a system in the public domain I would appreciate it if you would send me mail telling me: 1. What the system is written in (particularly interested in yacc/lex/C, as we run Eunice and this will be easily extendable). 2. some brief summary of what the program will/will not automate in its present incarnation. 3. Who I should get in touch with to get the source. Thank you in advance, Jonathan S. Shapiro Haverford College -- Jonathan S. Shapiro Haverford College "It doesn't compile pseudo code... What do you expect for fifty dollars?" - M. Tiemann
jtp@lasspvax.UUCP (Garry Wiegand) (11/20/85)
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)