[Suggestion] More deprecation features

BCS ao at pathlink.com
Thu Jul 17 16:58:29 PDT 2008


Reply to Stewart,

> "BCS" <ao at pathlink.com> wrote in message
> news:55391cb32f4938cab635e371a9d8 at news.digitalmars.com... <snip
> excessive quote>
> 
>> Another solution would be to rename the old function (foo -> foo_int)
>> patch up all internal references and then make a deprecated wrapper
>> function or alias to make the external calls work.
>> 
> Yes, that's one way of achieving some cases of idea 1....
> 
>> That patch up should be doable because if you don't have that code in
>> hand. it probably isn't internal.
>> 
> What do you mean by this?
> 

excluding the cases of code going from export to public the programmer who 
is deprecating the old function more than likely also maintains any code 
that legitimately should have access to the new non deprecated version. Therefor 
they can patch up the names them self. For that one exception, that above 
trick would be a breaking change.

> Stewart.
> 





More information about the Digitalmars-d mailing list