digitalmars.D.announce - Re: Descent with compile-time debug for testing
- Pablo Ripolles <in-call gmx.net> Jun 01 2009
- Ary Borenszweig <ary esperanto.org.ar> Jun 01 2009
- Pablo Ripolles <in-call gmx.net> Jun 01 2009
- BCS <ao pathlink.com> Jun 01 2009
- Pablo Ripolles <in-call gmx.net> Jun 01 2009
- Ary Borenszweig <ary esperanto.org.ar> Jun 01 2009
- Pablo Ripolles <in-call gmx.net> Jun 01 2009
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 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 improved or what is wrong, etc. As always, you can update from Eclipse itself as described here: http://www.dsource.org/projects/descent And now a little explanation about how to get it working: right click on the function call or template instance you want to debug at compile-time, select Source -> Debug at Compile-Time, and that's it! The debugger interface will appear and you can step-into/over/return, or continue, place breakpoints (but not yet in external files, sorry,) and also it will break on errors, and you'll have the full stack trace to see what went wrong. :-) (maybe I'll do a video about this later, for the curious) Just note that if you do this: --- int foo(int x) { return x * 2; } void main() { int x = foo(10); } --- if you try to debug "foo(10)", it will show the debugger interface, but stepping into will end the debugging session. Why? Because in the semantic analysis for that code, the call "foo(10)" isn't evaluated at compile time (as Descent just sneaks into the normal semantic analysis of the module.) For this you have to write: void main() { const x = foo(10); } and now "foo(10)" is evalauted at compile time, since it's return value is assigned to a const value. ("const int" will also work.) In the execution, you can see variables, analyze expressions (it supports any kinf of expression, like writing "1 + 2*3" will print "7".) This is only for D1, in D2 it will not work as expected. Enjoy!
Jun 01 2009
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?
Jun 01 2009
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 Borenszweig Wrote: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?
Jun 01 2009
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
somewhere there should be a ".log" file that has alls sorts of goodies like stacktraces for the error and the like.Thanks! Ary Borenszweig Wrote:And what's on the Error Log?
Jun 01 2009
Content-Type: text/plain OK there you go! Let's see if this helps. Thanks! BCS Wrote: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
somewhere there should be a ".log" file that has alls sorts of goodies like stacktraces for the error and the like.Thanks! Ary Borenszweig Wrote:And what's on the Error Log?
Jun 01 2009
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 should be fixed. Please tell me if this happened and you had at least one D project in the workspace... Pablo Ripolles wrote:OK there you go! Let's see if this helps. Thanks! BCS Wrote: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
stacktraces for the error and the like.Thanks! Ary Borenszweig Wrote:And what's on the Error Log?
Jun 01 2009
Pablo Ripolles <in-call gmx.net> 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 should be fixed. Please tell me if this happened and you had at least one D project in the workspace... Pablo Ripolles wrote:OK there you go! Let's see if this helps. Thanks! BCS Wrote: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
stacktraces for the error and the like.Thanks! Ary Borenszweig Wrote:And what's on the Error Log?
Jun 01 2009