October 13, 2013
Found one issue :

A call to std.functional.memoize crashes with the following error:

object.Error: TypeInfo.compare is not implemented
----------------
./rossignol(const(pure nothrow @trusted int function(const(void*), const(void*))) object.TypeInfo_Struct.compare+0x3a) [0x89b3032]
./rossignol(_aaInX+0x4d) [0x89b7f9d]
./rossignol(immutable(char)[] std.functional.memoize!(_D3xml10attributes5name_FKxS3xml10attributes9AttributeZAya).memoize(ref const(xml.attributes.Attribute))+0x44) [0x878b954]
October 13, 2013
On 10/13/2013 4:01 AM, Olivier Pisano wrote:
> Found one issue :
>
> A call to std.functional.memoize crashes with the following error:
>
> object.Error: TypeInfo.compare is not implemented
> ----------------
> ./rossignol(const(pure nothrow @trusted int function(const(void*),
> const(void*))) object.TypeInfo_Struct.compare+0x3a) [0x89b3032]
> ./rossignol(_aaInX+0x4d) [0x89b7f9d]
> ./rossignol(immutable(char)[]
> std.functional.memoize!(_D3xml10attributes5name_FKxS3xml10attributes9AttributeZAya).memoize(ref
> const(xml.attributes.Attribute))+0x44) [0x878b954]

Please file bug reports on Bugzilla!
October 14, 2013
Am 13.10.2013 00:16, schrieb Walter Bright:
> http://ftp.digitalmars.com/dmd2beta.zip

This zip does not contain the latest version of Optlink.
The one at http://ftp.digitalmars.com/optlink.zip seems to be newer.

Kind Regards
Benjamin Thaut
October 14, 2013
On 10/14/2013 12:50 AM, Benjamin Thaut wrote:
> Am 13.10.2013 00:16, schrieb Walter Bright:
>> http://ftp.digitalmars.com/dmd2beta.zip
>
> This zip does not contain the latest version of Optlink.
> The one at http://ftp.digitalmars.com/optlink.zip seems to be newer.

That one is dated 04-10-13, while the one in the zip file is dated 08/28/13, so I'm not sure why the former is newer.
October 14, 2013
Am 14.10.2013 10:59, schrieb Walter Bright:
> On 10/14/2013 12:50 AM, Benjamin Thaut wrote:
>> Am 13.10.2013 00:16, schrieb Walter Bright:
>>> http://ftp.digitalmars.com/dmd2beta.zip
>>
>> This zip does not contain the latest version of Optlink.
>> The one at http://ftp.digitalmars.com/optlink.zip seems to be newer.
>
> That one is dated 04-10-13, while the one in the zip file is dated
> 08/28/13, so I'm not sure why the former is newer.

My bad. German dates... We write the the day first then the month and then the year.
October 14, 2013
On Mon, Oct 14, 2013 at 11:35 AM, Benjamin Thaut <code@benjamin-thaut.de>wrote:

> My bad. German dates... We write the the day first then the month and then the year.
>

Americans seem to read dates as "October 14th, 2013" which is way they write numeric dates in such an odd way :D.

Since I realized that is the reason for it I've been much better at noticing the location of a person who wrote a date down.


October 14, 2013
Am 13.10.2013 00:16, schrieb Walter Bright:
> http://ftp.digitalmars.com/dmd2beta.zip
>
> Current list of regressions:
>
> http://d.puremagic.com/issues/buglist.cgi?query_format=advanced&bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
>
>
> This isn't a release candidate, in particular the documentation needs
> work, but we need to shake the tree for any undetected regressions.
>
> Further beta announcements go in the dmd-beta mailing list.
>
> Note that this release contains:
>
> 29 enhancements
> 307 dmd bugs fixed
> 14 druntime bugs fixed
> 73 phobos bugs fixed

I just upgraded to dmd 2.064 and there are most likely multiple new struct lifetime bugs. I'm going to file them as soon as I find them, but first I have to get the debugger working again. The patch I used for dmd to be able to debug D programs with visual studio no longer works for dmd 2.064.
October 14, 2013
Am 14.10.2013 15:14, schrieb Benjamin Thaut:
> Am 13.10.2013 00:16, schrieb Walter Bright:
>> http://ftp.digitalmars.com/dmd2beta.zip
>>
>> Current list of regressions:
>>
>> http://d.puremagic.com/issues/buglist.cgi?query_format=advanced&bug_severity=regression&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
>>
>>
>>
>> This isn't a release candidate, in particular the documentation needs
>> work, but we need to shake the tree for any undetected regressions.
>>
>> Further beta announcements go in the dmd-beta mailing list.
>>
>> Note that this release contains:
>>
>> 29 enhancements
>> 307 dmd bugs fixed
>> 14 druntime bugs fixed
>> 73 phobos bugs fixed
>
> I just upgraded to dmd 2.064 and there are most likely multiple new
> struct lifetime bugs. I'm going to file them as soon as I find them, but
> first I have to get the debugger working again. The patch I used for dmd
> to be able to debug D programs with visual studio no longer works for
> dmd 2.064.

I'm also getting random missing symbol linker errors with both dmd 2.063.2 and dmd 2.064. But only on 32-bit windows. On 64-bit windows it works fine.
This is really frustrating...
October 14, 2013
On 10/14/2013 04:59 AM, Rory McGuire wrote:
> On Mon, Oct 14, 2013 at 11:35 AM, Benjamin Thaut <code@benjamin-thaut.de
> <mailto:code@benjamin-thaut.de>> wrote:
>
>     My bad. German dates... We write the the day first then the month
>     and then the year.
>
>
> Americans seem to read dates as "October 14th, 2013" which is way they
> write numeric dates in such an odd way :D.
>
> Since I realized that is the reason for it I've been much better at
> noticing the location of a person who wrote a date down.
>
>

*BOTH* of you write dates in an odd way.

http://xkcd.com/1179/
October 14, 2013
On Monday, 14 October 2013 at 10:00:01 UTC, Rory McGuire wrote:
> On Mon, Oct 14, 2013 at 11:35 AM, Benjamin Thaut <code@benjamin-thaut.de>wrote:
>
>> My bad. German dates... We write the the day first then the month and then
>> the year.
>>
>
> Americans seem to read dates as "October 14th, 2013" which is way they
> write numeric dates in such an odd way :D.
>
> Since I realized that is the reason for it I've been much better at
> noticing the location of a person who wrote a date down.

I've chosen to try writing dates using the ISO

2013-10-14

Always causes confusion, thus leading people to actually figure out the numbers. :) Of course programmers don't have an issue with it. Sadly, it can't be shortened:

13-10-14 or 10-14

I'm also ok with 2013/10/14 even though ISO isn't.