Path.modified(name) same as Path.created(name) if modified now

Can you try this code out? I think this is related to a compiler bug which I just added (http://d.puremagic.com/issues/show_bug.cgi?id=2232)

import Path = tango.io.Path;
auto name = "D:\\test.txt";
assert(Path.timeStamps(name).modified == Path.timeStamps(name).created);

If this version works (meaning, the assert throws), then you are probably running into the same bug.

bug:

import Path = tango.io.Path;
auto name = "D:\\test.txt";
assert(Path.modified(name).ticks == Path.created(name).ticks);

Seems this version works, thanks.

import Path = tango.io.Path;
auto name = "D:\\test.txt";
assert(Path.timeStamps(name).modified.ticks == Path.timeStamps(name).created.ticks);

Does the version I proposed not work unless you use the 'ticks' to compare? I'm just curious :)

more details:

        auto name = "D:\\test.txt";
        auto modified = Path.modified(name);
        auto created = Path.created(name);
        Stdout.formatln("modified {}", modified.ticks); //633517142269165056
        Stdout.formatln("created {}", created.ticks);   //633517142269165056
        assert(modified.ticks == created.ticks );       //true
        assert(modified == created );                   //true

        assert(Path.modified(name) == Path.created(name)); //failure
        assert(Path.modified(name).ticks == Path.created(name).ticks); //failure

another bug, Driver D:\ is FAT32 format, but Path.timeStamps(name).created returns UTC time.

        Return timestamp information

        Timstamps are returns in a format dictated by the 
        file-system. For example NTFS keeps UTC time, 
        while FAT timestamps are based on the local time

FS.Stamps timeStamps (char[] name)
{
        char[512] tmp = void;
        return FS.timeStamps (FS.strz(name, tmp));
}

seems I should use phobos version in tangobos, not use tango version

The bug of the title is a compiler bug, and will be moved to the relevant "External bugs" milestone.

The UTC problem should get its own ticket.

And please do not set the milestone, it is for administration use only, use Version field to indicate the version error applies to.

See #1194 for UTC problems.

Can you retest this with the latest compiler (1.034)? According to the log, the compiler bug has been fixed.

If it now works, please close as fixed.

tested with DMD 1.035, seems fixed now.