http://d.puremagic.com/issues/show_bug.cgi?id=9331
--- Comment #2 from [email protected] 2013-02-08 22:23:12 PST --- Hmm, this is very strange. I found that the bug only happens with the exact code posted above. I was testing a program that just printed the value of ulong.max, and it was correct. But the above code does indeed display the bug! Then I added "pragma(msg, ulong.max)" and it displays the correct value. Furthermore, commenting out "writefln("%d\n", u4)" causes the right value to be printed when running the program. Looks like there may be some kind of stack corruption or template crosstalk, not really directly related to the value of ulong.max. Will investigate this odd issue more carefully... -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
