On Monday, 14 October 2013 at 13:25:23 UTC, Benjamin Thaut wrote:
> 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...

I've encountered this too. I'll try to reduce, but the test case isn't easy.

On 10/14/2013 2:35 AM, Benjamin Thaut wrote:
> My bad. German dates... We write the the day first then the month and then the
> year.

Yah, that is terribly confusing, especially considering the global intarnets.

I tend to write dates as year-month-day, that way they sort properly in a directory listing :-)

On 10/14/2013 6:25 AM, Benjamin Thaut wrote:
> 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...

Is it possible you are linking together code compiled with different command line -version or -debug switches?

On Monday, 14 October 2013 at 19:17:25 UTC, 1100110 wrote:
> *BOTH* of you write dates in an odd way.
>
> http://xkcd.com/1179/

Amen. ISO 8601 FTW.

The Japanese got it correct natively though. It's year, then month then day, seperated either by explicit 年月日 (year, month, day), or by "/" or "-". At university, we mostly used "-".

Well, that's when they don't use their imperial dates :/

On Monday, 14 October 2013 at 20:39:12 UTC, Jesse Phillips wrote:
> 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.

It minimum, I try to keep it to "YYYY.*MM.*DD".

Also, when naming files, it sorts automatically, which is always good. That's how I name my photos anyways: format("%04-%02 - LOCATION_OR_EVENT - %03", year, month, ++counter).

On Monday, 14 October 2013 at 21:21:29 UTC, monarch_dodra wrote:
> On Monday, 14 October 2013 at 19:17:25 UTC, 1100110 wrote:
>> *BOTH* of you write dates in an odd way.
>>
>> http://xkcd.com/1179/
>
> Amen. ISO 8601 FTW.
>
> The Japanese got it correct natively though. It's year, then month then day, seperated either by explicit 年月日 (year, month, day), or by "/" or "-". At university, we mostly used "-".
>
> Well, that's when they don't use their imperial dates :/
>

Yes, they are pretty good at choosing completely confusing norms, but on that one they did good :D

On Monday, October 14, 2013 14:18:33 Walter Bright wrote:
> On 10/14/2013 2:35 AM, Benjamin Thaut wrote:
> > My bad. German dates... We write the the day first then the month and then the year.
> 
> Yah, that is terribly confusing, especially considering the global intarnets.
> 
> I tend to write dates as year-month-day, that way they sort properly in a directory listing :-)

Exactly. It sorts great that way and is nice and clear. It's also what's done in the standard ISO date formats.

- Jonathan M Davis

On Monday, 14 October 2013 at 21:18:32 UTC, Walter Bright wrote:
> Yah, that is terribly confusing, especially considering the global intarnets.

I get bitten by it locally too: if there's a test with an inaccurate sql query with time formatted as string, the sql server doesn't always compute it, because the default "human-readable" time format is taken from the current locale, and to parse it one first has to guess the format itself, which is quite difficult in a heterogeneous system.

On Tuesday, 15 October 2013 at 04:41:13 UTC, Kagamin wrote:
> On Monday, 14 October 2013 at 21:18:32 UTC, Walter Bright wrote:
>> Yah, that is terribly confusing, especially considering the global intarnets.
>
> I get bitten by it locally too: if there's a test with an inaccurate sql query with time formatted as string, the sql server doesn't always compute it, because the default "human-readable" time format is taken from the current locale, and to parse it one first has to guess the format itself, which is quite difficult in a heterogeneous system.

This is for that very reason that I prefers to work with timestamps UTC as much as possible. No timzone hell, no format hell, no nothing. Just convert from user input directly, and convert back to text just before output.

On Saturday, 12 October 2013 at 22:16:13 UTC, Walter Bright wrote:
> 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 want to thank you and also especially Kenji who has been crazy fast at fixing the regressions I have encoutered. Now everything work, and several bug I was hitting in 2.063 are fixed. Good job !

On 2013-10-15 07:16, deadalnix wrote:

> This is for that very reason that I prefers to work with timestamps UTC
> as much as possible. No timzone hell, no format hell, no nothing. Just
> convert from user input directly, and convert back to text just before
> output.

Agree. Always work with universal standards internally in your applications. Be it time, date, encodings or whatever. Then convert to and from local formats, as early as possible on input and as late as possible for output.

-- 
/Jacob Carlborg