There are a few more 64 bugs that I'm aware of and haven't filed yet,
too. I was taking my time for a combination of reasons:
1. Going from a 1k line file with a failing unittest to a decent test
case is tedious work and I only have the patience to do maybe one a night.
2. I think a lot of the failing unittests in my code may be symptoms of
the same bug. If I wait for one bug to be fixed before filing another,
I can avoid a lot of wasted work.
3. I was under the impression that if I went any faster, I would no
longer be the bottleneck.
4. If anyone else is heavily testing the 64 compiler, they may stumble
on an easier to reproduce version of the bug.
On 2/11/2011 1:38 AM, Walter Bright wrote:
2 more 64 bit bugs were posted today.
Don Clugston wrote:
Since the last release
- A rather terrible appending regression was fixed (adequate grounds
for an emergency release)
- Some of the worst wrong code bugs have been fixed
- A raft of other bugs have been fixed.
- And we've switched to git!
I really think we should be wrapping up a release now.
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
