Reply to thread

Message: [QUOTE="Chris Dollin, post: 2475461"] Unless there's something else going on that you haven't mentioned yet, this seems unlikely. Such translation is probably best done by people, and done in such a way as to reduce or eliminate the code that "needs to be different". Unless you understand what the differences /are/, automated assistance isn't likely to help. It's /possible/ that whoever said you needed Lex and Yacc thought that you'd need to rewrite the code to use them as part of the migration. (You very likely don't.) Or it's possible that the AB compiler is written using them (Lex and Yacc, or Flex and Bison, turn descriptions of languages into C code [well, tables for C code]) and migrating it will need to migrate the lexis and grammar. If that's so, comp.lang.c is the wrong place to ask about the Lex and Yacc bits. There are more appropriate newsgroups; I'd try asking in comp.programming or comp.compilers. The C code you present looks fine (assuming that all the undefined names are defined in suitable header files). 42Kb of code isn't much, unless you really meant 42K /lines/. The problems will come when you try and compiler it, and then when you try and run it (hopefully there are tests suites you can run to make sure it's migrated reasonably safely). [/QUOTE]