Re: Descent with compile-time debug for testing

Steve Teale wrote: Bill Baxter Wrote: On Wed, Jun 10, 2009 at 10:55 AM, Steve Tealesteve.te...@britseyeview.com wrote: Trass3r Wrote: Ary Borenszweig schrieb: That's ddbg working wrong, not Descent. :-P Ah, damn so no way this gets fixed. Debugging D is a pain :( So is ddbg dead?

Re: Descent with compile-time debug for testing

Trass3r Wrote: Ary Borenszweig schrieb: That's ddbg working wrong, not Descent. :-P Ah, damn so no way this gets fixed. Debugging D is a pain :( So is ddbg dead?

Re: Descent with compile-time debug for testing

On Wed, Jun 10, 2009 at 10:55 AM, Steve Tealesteve.te...@britseyeview.com wrote: Trass3r Wrote: Ary Borenszweig schrieb: That's ddbg working wrong, not Descent. :-P   Ah, damn so no way this gets fixed. Debugging D is a pain :( So is ddbg dead? Author hasn't been heard from round here

Re: Descent with compile-time debug for testing

Ary Borenszweig schrieb: That's ddbg working wrong, not Descent. :-P Ah, damn so no way this gets fixed. Debugging D is a pain :(

Re: Descent with compile-time debug for testing

Thanks for your hard work! Are there plans to improve ddbg support? I'm getting parser errors: -APC10goldengine5token5Token class goldengine.token.Token*[] -Parser: (1:0): found [, expected Ident input: [0] lookahead: [ lexeme: \[ AST node stack: Deref Cast Ident LR stack: State 4 (1:1)

Re: Descent with compile-time debug for testing

Trass3r escribió: Thanks for your hard work! Are there plans to improve ddbg support? I'm getting parser errors: -APC10goldengine5token5Token class goldengine.token.Token*[] -Parser: (1:0): found [, expected Ident input: [0] lookahead: [ lexeme: \[ AST node stack: Deref Cast Ident LR stack:

Re: Descent with compile-time debug for testing

I do not why but every time I install Descent into my Eclipse 3.4.2 on MacOSX, on the exit (quiting eclipse) it gives me a JavaNullPointer error... it's a pity. Cheers! Ary Borenszweig Wrote: Hi! I just uploaded a new test version of Descent (0.5.6) with the new compile-time debugging

Re: Descent with compile-time debug for testing

Pablo Ripolles escribió: I do not why but every time I install Descent into my Eclipse 3.4.2 on MacOSX, on the exit (quiting eclipse) it gives me a JavaNullPointer error... it's a pity. Cheers! And what's on the Error Log?

Re: Descent with compile-time debug for testing

Hello, just before it closes there appears a window message tittled Problems saving worksppace and the message is: Problems occurred while trying to save the state of the workbench. On details it's written: Problems ocurred during save. java.lang.NullPointerException Thanks! Ary

Re: Descent with compile-time debug for testing

Reply to Pablo, Hello, just before it closes there appears a window message tittled Problems saving worksppace and the message is: Problems occurred while trying to save the state of the workbench. On details it's written: Problems ocurred during save. java.lang.NullPointerException

Re: Descent with compile-time debug for testing

Hello Ary! Yes indeed, it is fixed! and yes, I had no D project on that workspace. Thanks! Ary Borenszweig Wrote: Hmm, that's strange. You should only get that error if you don't have any D project in the workspace. Anyway, it's a bug and I fixed it, you can update from Eclipse and it

Descent with compile-time debug for testing

Hi! I just uploaded a new test version of Descent (0.5.6) with the new compile-time debugging feature. I tested it with some functions and templates and it seems to be working (but not with string mixins,) so I wanted you to play with it a little and see what you think, what could be