http://www.digitalmars.com/d/changelog.html

Walter Bright wrote:
> 
> http://www.digitalmars.com/d/changelog.html

Walter, thank you!!

L.

Walter Bright wrote:

> http://www.digitalmars.com/d/changelog.html

(or http://www.digitalmars.com/d/changelog.html#new0155,
to avoid all that scrolling when one reads this later...)

> # Removed std.recls, instead use http://synesis.com.au/software/recls/.

This will also avoid the C++ requirement for building Phobos,
while still allowing you to get a new version of recls later.

It also works around the "documentation issue" of std.recls.


Now all we need is an upgrade for zlib: 1.2.1 -> 1.2.3
http://www.zlib.net/zlib123.zip

I believe the current version has some security problems...
http://www.kb.cert.org/vuls/id/238678
http://www.kb.cert.org/vuls/id/680620
Or has these been patched in the DMD version of zlib 1.2.1 ?


But it looks like a solid update, let's see if we can
upgrade GDC with all of them since it's at DMD 140 now.

--anders

Walter Bright wrote:
> 
> http://www.digitalmars.com/d/changelog.html

The attached windbg debugger is a little bit wierd.
Font is too small ... hard to see things.
When you open a "program", all the other "source" windows disappear.
Does't seem to see local variables very well?

Walter Bright wrote:
> 
> http://www.digitalmars.com/d/changelog.html

Thank you, Walter.
I hope you redistribute windbg in a separate package next time.

Wang Zhen wrote:
> Walter Bright wrote:
>>
>> http://www.digitalmars.com/d/changelog.html
> 
> Thank you, Walter.
> I hope you redistribute windbg in a separate package next time.

It's the debugger everybody's been waiting for!(From 1996 nonetheless)

L.

Walter Bright wrote:
> 
> http://www.digitalmars.com/d/changelog.html

Awesome.  These fixes may be just enough to get Tuple working.  And the debugger to boot!  Thanks, Walter :-)


Sean

This bug (crash in gcx.mark() when using several threads) should probably be
closed too:

http://d.puremagic.com/bugzilla/show_bug.cgi?id=114



Walter Bright wrote:

> 
> http://www.digitalmars.com/d/changelog.html

Walter Bright wrote:
> 
> http://www.digitalmars.com/d/changelog.html

You are as I always say, one of the men. (not THE man though, sorry)

Wang Zhen wrote:
> Walter Bright wrote:
>> 
>> http://www.digitalmars.com/d/changelog.html
> 
> Thank you, Walter.
> I hope you redistribute windbg in a separate package next time.

The windbg that comes with dmd 0.155 is useless for me, because it runs so slow it looks like it hangs when I try to run an app with it.  I didn't change any of it's settings, so it doesn't seem to work out of the box for me.  Anyone else experienced this?

But windbg 6 (which I got from Microsoft's site) works fine most of the time.  What exactly am I missing out on by not using the old version?

I've only used it for debugging access violations so far, which seems to work.  And it opens the source code file and shows in which function the violation occurred.  Seems that line numbers might be missing, since it only show which function call (call stack), not the exact line in that function.

It would be really nice to have some recommandations for how to use windbg, pros and cons for each version etc.  Other than the windbg 6 tutorial link ( http://mtaulty.com/blog/(e4b1ut55q0wf0545z043zsm5)/archive/2004/08/03/608.aspx ).

Would be even nicer if the D runtime would print line numbers itself on access violations. Or a full stack trace. :)