Sorry, forgot to say that..
Because I use assertions. I can do just:
export OCAMLRUNPARAM=b=1
make all
make test
and then examine the callstack to see where something went wrong.
The above works only for bytecode (callstack).
But asserts print out the file:line information where the assertion
failed. So if something goes wrong, you always get notified and can see
easily what went wrong and where.
Best regards,
Janne Hellsten
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
