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 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!
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 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?
Re: Taunting
Reply to Ary, (I came to this conclusion when trying to debug the scrapple:units project). I'm sorry g OTOH that is a rater pathological cases. One option that might be doable (I don't know how the inside works so I'm guessing here) is to have the debug more highlight expression that can undergo CTFE and constant folding. The user would work by selecting an expression and it would be replace with it's value. to make things manageable, long string expressions could be truncated and accessed via pop up and as for string mixins, run the result thought the general code formatter.
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 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?
ODBCD
I have an alpha version of an ODBCD working. I have tested it so far with MySQL and SQL Express 2005 on Windows XP. Both have their shortcomings, but I don't think they have that much to do with the ODBCD code. If you have a different database and/or ODBC driver, and are interested in testing/helping, please email me and I'll send you a zip. It's quite small and relatively easy to work with, since ODBC drivers tend to produce pretty reasonable error information, but it still needs a lot of work. This will eventually be part of DCat - http://www.britseyeview.com/dcat/ - however because ODBC now seems to be on everyone else's back burner I'm thinking of trying some closer-to-native implementations as well. Steve
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 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 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?
