Author: prino
Posted: Mon Jul 25, 2016 3:22 pm (GMT 5.5)
At one client we used the following:
First step is to change your compile procedures in the development environment to use both compilers sequentially, so that you can see what errors old source and a new compiler generate, but you can still continue running the code - in other words ignore any RC>4 from the new compiler for now, but let it trigger a step containing a SEND (to the user) message, to thoroughly check the listing of the new compiler, and change the code to remove them.
Once you're fairly confident that you've found the real show-stoppers, change the setup to stop your compile jobs if the new compiler issues any RC>4, and continue using both sequentially, but now run the code generated by the new compiler.
_________________
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
No programming here (yet)![icon_smile.gif]()
Posted: Mon Jul 25, 2016 3:22 pm (GMT 5.5)
At one client we used the following:
First step is to change your compile procedures in the development environment to use both compilers sequentially, so that you can see what errors old source and a new compiler generate, but you can still continue running the code - in other words ignore any RC>4 from the new compiler for now, but let it trigger a step containing a SEND (to the user) message, to thoroughly check the listing of the new compiler, and change the code to remove them.
Once you're fairly confident that you've found the real show-stoppers, change the setup to stop your compile jobs if the new compiler issues any RC>4, and continue using both sequentially, but now run the code generated by the new compiler.
_________________
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
No programming here (yet)
