Re: Do not use 2.041

2010-03-12 Thread Nick Sabalausky
"bearophile" wrote in message news:hnd8hr$1q6...@digitalmars.com... > Fawzi Mohamed: >> Yes tango has it, there are a couple of things that are a bit clumsy, >> due to backward compatibility to previous implementations, but I think >> that the basic approach is sound: > > A nice stack trace is a

Re: Do not use 2.041

2010-03-12 Thread bearophile
Fawzi Mohamed: > Yes tango has it, there are a couple of things that are a bit clumsy, > due to backward compatibility to previous implementations, but I think > that the basic approach is sound: A nice stack trace is a quite significant improvement when I program in D. It helps solve problem

Re: Do not use 2.041

2010-03-11 Thread Fawzi Mohamed
On 11-mar-10, at 22:09, Steven Schveighoffer wrote: On Thu, 11 Mar 2010 16:05:51 -0500, bearophile > wrote: Steven Schveighoffer: Also if we get exception stack trace support, then you can immediately see everything. It's probably better to focus on that. OK. Do you want me to remove th

Re: Do not use 2.041

2010-03-11 Thread Robert Clipsham
On 11/03/10 20:28, Steven Schveighoffer wrote: If a good debugger existed for dmd, you could determine the location, but I don't know of any good ones. gdb doesn't do a very good job with D. -Steve I've never had a problem with GDB, it's always worked fine for me, for everything I've used (in

Re: Do not use 2.041

2010-03-11 Thread Trass3r
Note to everyone, dmd 2.041 array allocation is broken (inadvertently by my array append patch). You should not use this release. Another big problem of the release is operator overloading.

Re: Do not use 2.041

2010-03-11 Thread Trass3r
If a good debugger existed for dmd, you could determine the location, but I don't know of any good ones. gdb doesn't do a very good job with D. On Windows cv2pdb + Visual Studio works pretty damn well for me. Can't compare it to gdb though, since I haven't used that yet.

Re: Do not use 2.041

2010-03-11 Thread Trass3r
stacktrace printout, there is a need for such things. But I think exception tracing is coming, I think Tango already has it. Tango has it since a long time. Makes me wonder why it hasn't been ported to druntime, I thought the runtimes are quite similar.

Re: Do not use 2.041

2010-03-11 Thread Trass3r
I did use it, ddbg worked good (but always skipped over runtime functions, which is annoying when you are developing the runtime). I hope that this problem eventually is solved. Isn't ddbg totally abandoned?

Re: Do not use 2.041

2010-03-11 Thread Steven Schveighoffer
On Thu, 11 Mar 2010 16:14:36 -0500, grauzone wrote: Steven Schveighoffer wrote: If a good debugger existed for dmd, you could determine the location, but I don't know of any good ones. gdb doesn't do a very good job with D. dmd has produced debugging information that makes gdb choke up f

Re: Do not use 2.041

2010-03-11 Thread grauzone
Steven Schveighoffer wrote: If a good debugger existed for dmd, you could determine the location, but I don't know of any good ones. gdb doesn't do a very good job with D. dmd has produced debugging information that makes gdb choke up for ages. This makes gdb (and some other utilities that tr

Re: Do not use 2.041

2010-03-11 Thread Steven Schveighoffer
On Thu, 11 Mar 2010 16:05:51 -0500, bearophile wrote: Steven Schveighoffer: Also if we get exception stack trace support, then you can immediately see everything. It's probably better to focus on that. OK. Do you want me to remove those two bug reports then? I think they should at lea

Re: Do not use 2.041

2010-03-11 Thread bearophile
Steven Schveighoffer: > Also if we get exception stack trace support, then you can immediately see > everything. It's probably better to focus on that. OK. Do you want me to remove those two bug reports then? Bye, bearophile

Re: Do not use 2.041

2010-03-11 Thread bearophile
Steven Schveighoffer: > The compiler > would have to instrument all allocations/calls to the runtime functions > with line number arguments. Do you suggest me to mark my bug report as Invalid then? There's another similar bug report: http://d.puremagic.com/issues/show_bug.cgi?id=3851 Debugge

Re: Do not use 2.041

2010-03-11 Thread Steven Schveighoffer
On Thu, 11 Mar 2010 15:28:36 -0500, Steven Schveighoffer wrote: On Thu, 11 Mar 2010 15:20:38 -0500, bearophile wrote: Steven Schveighoffer: If you want to use the new release without the bugs, please apply this patch to druntime: http://www.dsource.org/projects/druntime/changeset?forma

Re: Do not use 2.041

2010-03-11 Thread Steven Schveighoffer
On Thu, 11 Mar 2010 15:20:38 -0500, bearophile wrote: Steven Schveighoffer: If you want to use the new release without the bugs, please apply this patch to druntime: http://www.dsource.org/projects/druntime/changeset?format=diff&new=262&old=260&new_path=trunk&old_path=trunk I have just ad

Re: Do not use 2.041

2010-03-11 Thread bearophile
Steven Schveighoffer: > If you want to use the new release without the bugs, please apply this > patch to druntime: > > http://www.dsource.org/projects/druntime/changeset?format=diff&new=262&old=260&new_path=trunk&old_path=trunk I have just added a small bug report, I don't know if this can int

Do not use 2.041

2010-03-11 Thread Steven Schveighoffer
On Mon, 08 Mar 2010 01:54:12 -0500, Walter Bright wrote: Lots of meat and potatoes here, and a cookie! (spelling checker for error messages) http://www.digitalmars.com/d/1.0/changelog.html http://ftp.digitalmars.com/dmd.1.057.zip http://www.digitalmars.com/d/2.0/changelog.html http://f