Compiler updating user code

Daniel Murphy yebbliesnospam at gmail.com
Fri Mar 14 07:33:44 PDT 2014


"Frustrated"  wrote in message news:qkldntailmybifzsnwzn at forum.dlang.org...

> Could the compiler itself be configured in such a way(at least for most 
> "breaking changes") that the user could switch the change on and off yet 
> keep the fixes.

It already is, breaking changes are first introduced as warnings, then as 
deprecations, then as errors.  While in the first two stages you can switch 
them on and off.

> Possibly with the proper software and methodologies it could be done. It 
> would, at least, solve the problem. If someone didn't want some breaking 
> change they simply could remove it from the compiler: -removechange1435 
> (maybe change 1435 is final by default) which reverts the compiler back to 
> before that change BUT keeps all the fixes up to the current version that 
> are not dependent on that change.

Way too hard.  Not gonna happen.

> Suppose one can do the same with the compiler. Instead of downloading a 
> new version of a compiler one simply downloads the "fixes" and "changes". 
> If a change is added that one doesn't like they just uninstall it.

Also way too hard.  The current way works fine. 



More information about the Digitalmars-d mailing list