On Monday, April 02, 2012 18:51:50 Andrej Mitrovic wrote:
> On 4/2/12, Walter Bright <walter@digitalmars.com> wrote:
> > http://ftp.digitalmars.com/dmd2beta.zip
> 
> curdir and pardir have been deprecated on the basis that "." and ".." are used for these on all platforms. However I've noticed something in Python, this is in Lib\macpath.py:
> 
> # strings representing various path-related bits and pieces
> curdir = ':'
> pardir = '::'
> 
> So it seems there is a use-case for keeping curdir/pardir in Phobos and the above should probably be added. Another little use-case is that removing these breaks user-code for no reason other than saving two lines of code in Phobos.

That decision was made months ago during the review of the new std.path, and I could have remembered the reasoning wrong. But curdir and pardir would have been going away as part of the std.path changes regardless, because they're not properly camelcased. So, it's only a question of whether it would have meant changing curdir and pardir to "." and ".." or to something like currentDir and parentDir. User code would have had to change either way.

- Jonathan M Davis
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

This is happening to me too. See the bug I posted. My case is much different than yours.

http://d.puremagic.com/issues/show_bug.cgi?id=7811

Sent from my iPhone

On Apr 2, 2012, at 8:59 AM, "David Nadlinger" <code@klickverbot.at> wrote:

> There also seems to be a regression regarding mixin templates – I'm getting »Error: not a property s.isSetFlags«, where isSetFlags is a plain field (i.e. not a @property) of s added via a mixin template, but as the error occurs deep inside CTFE-generated code, I don't yet have a test case for this one either.

On 3 Apr 2012, at 5:01, Steven Schveighoffer wrote:
> This is happening to me too. See the bug I posted. My case is much different than yours.
>
> http://d.puremagic.com/issues/show_bug.cgi?id=7811


Turns out that the error message was actually »correct«, but triggered by another regression:

http://d.puremagic.com/issues/show_bug.cgi?id=7815

David
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Mon, Apr 2, 2012 at 1:13 AM, Walter Bright <walter@digitalmars.com> wrote:
> http://ftp.digitalmars.com/dmd1beta.zip http://ftp.digitalmars.com/dmd2beta.zip

Regression in dmd 1.074 beta http://d.puremagic.com/issues/show_bug.cgi?id=7817

Cheers, Jakob.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

I just found what I think is a regression involving the import system.  I'm DustMiteing it right now, should have a bug report by tonight.

On 4/1/2012 7:13 PM, Walter Bright wrote:
> http://ftp.digitalmars.com/dmd1beta.zip
> http://ftp.digitalmars.com/dmd2beta.zip
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

I've hit another regression:

struct Test {
    static immutable c = Test();
    static if( true ){}
}

when compiled with no options gives

Error: static if conditional cannot be at global scope

Changing to

struct Test {
    static immutable Test c = Test();
    static if( true ){}
}

does not trigger the error.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

[D2 Beta] Cannot use getHash in toHash without a warning
http://d.puremagic.com/issues/show_bug.cgi?id=7826


_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

This should probably be mentioned in the changelog:

https://github.com/D-Programming-Language/tools/pull/25

And maybe the fact that --eval's import list has been updated as part of this:

https://github.com/D-Programming-Language/tools/pull/24

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

Was something changed with struct opCmp, or its signature, or "const" params? Because I'm getting some "wrong argument type" errors comparing some structs that use opCmp. I'll try to dig further into it and get a test case...

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

Might also consider bumping the date on the changelog to (closer to) whenever it's actually ready: If only because seeing "Released on April 1" probably doesn't instill a whole lot of confidence... ;) 

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta