A better way of managing backwards compatibility?

2015-09-03 Thread Prudence via Digitalmars-d
Dealing with changes to standardized interfacing such as api function names, namespaces, file names/module names, etc is usually impossible to do because it severs the code written before the change from the new compiler. Most people think this is the way to do it and there is no, better,

Re: A better way of managing backwards compatibility?

2015-09-03 Thread qznc via Digitalmars-d
On Thursday, 3 September 2015 at 17:48:23 UTC, Prudence wrote: 2. Write a translation process that essentially "updates" the source code to work. Lucky you: https://github.com/Hackerpilot/dfix

Re: A better way of managing backwards compatibility?

2015-09-03 Thread Prudence via Digitalmars-d
On Thursday, 3 September 2015 at 21:03:05 UTC, qznc wrote: On Thursday, 3 September 2015 at 17:48:23 UTC, Prudence wrote: 2. Write a translation process that essentially "updates" the source code to work. Lucky you: https://github.com/Hackerpilot/dfix There you go!! It seems someone just as