• Martin Nowak (16/16) Nov 26 2011 I just thought it would be useful to announce breaking changes, new
• Paul D. Anderson (6/29) Nov 26 2011 I don't know if we need a separate mailing list, but this information sh...
• Dejan Lekic (1/1) Nov 27 2011 D ChangeLog gives all such information, I believe.
• Xinok (4/5) Nov 27 2011 They are, but they're mixed with other changes and bug fixes. You have
• Martin Nowak (5/10) Nov 27 2011 And they are not focused on what needs to be changed in your code.

"Martin Nowak" <dawg dawgfoto.de> writes:

I just thought it would be useful to announce breaking changes, new  
warnings and deprecations
added to the D language (dmd, druntime, phobos) in a separate mailing list.
It can be also used to discourage from using certain constructs.

Some examples:
---
dmd >= 2.056

New Warning for dangling else.

Detailed explanation....
---
phobos >= 2.055

Deprecated std.path.basename. Replacement std.path.baseName.

Detailed explanation...
---

The actual message format should be machine parseable.

martin

Paul D. Anderson <paul.d.removethis.anderson comcast.andthis.net> writes:

Martin Nowak Wrote:

 I just thought it would be useful to announce breaking changes, new  
 warnings and deprecations
 added to the D language (dmd, druntime, phobos) in a separate mailing list.
 It can be also used to discourage from using certain constructs.
 
 Some examples:
 ---
 dmd >= 2.056
 
 New Warning for dangling else.
 
 Detailed explanation....
 ---
 phobos >= 2.055
 
 Deprecated std.path.basename. Replacement std.path.baseName.
 
 Detailed explanation...
 ---
 
 The actual message format should be machine parseable.
 
 martin

I don't know if we need a separate mailing list, but this information should 
be part of the change log and posted on the announcements mailing list.

For example, the deprecation listed above was described in the change log as:

• std.path has been rewritten from scratch and has a completely new API.

Seems like more is needed. Maybe a wiki page or something with a list of
deprecations scheduled along with build numbers and dates?

Paul

Dejan Lekic <dejan.lekic gmail.com> writes:

D ChangeLog gives all such information, I believe.

Xinok <xinok live.com> writes:

On 11/27/2011 7:01 AM, Dejan Lekic wrote:
 D ChangeLog gives all such information, I believe.

They are, but they're mixed with other changes and bug fixes. You have 
to read each item in the changelog to find the breaking changes. Listing 
them separately would help greatly when updating code.

"Martin Nowak" <dawg dawgfoto.de> writes:

On Sun, 27 Nov 2011 14:15:28 +0100, Xinok <xinok live.com> wrote:

 On 11/27/2011 7:01 AM, Dejan Lekic wrote:
 D ChangeLog gives all such information, I believe.

 They are, but they're mixed with other changes and bug fixes. You have  
 to read each item in the changelog to find the breaking changes. Listing  
 them separately would help greatly when updating code.

And they are not focused on what needs to be changed in your code.
But on a second thought it would be difficult to synchronize mails with
pull requests. Richer changelog entries could be of a help, submitted with  
the pull requests.