Re[2]: And if your head explodes.....
> Chris wrote....
>
>> I never even use the error reports from EU anyways.. It's much more
>> accurate and easier to understand if you debug it yourself..
>
>> Your code doesn't work? Add print statements .. systematically of
>> course..
>
> I agree. For the price I haven't found any language that suits my needs
> better.
> I also rarely need the Eu error report and I'm not much of a programmer.
>
> Like Chris, I find the best way to debug is to use print statements in my
> code to trap where the error is happening and where appropriate, to give
> me DOS window feedback about the state of my program just before it fails.
>
> The 300 line limit shouldn't stop you if you *really* can't afford to
> register.
>
> Mark
I totally agree with you, I used EU for ages before registering and
wrote some quite large programs (well over the 300 line limit:). Of
course when I finally did register it was very nice to suddenly have
error messages, took a while to adjust to using them :)
Another technique which I don't think anyone else has mentioned yet
(in this thread at least) is to brake your program in to smaller
chunks and test them individually, of course this isn't always
practical but sometimes it's usefully, I do this still even though I
have the registered version, it makes everything easier and more
robust.
Thomas Parslow (PatRat) ICQ #:26359483
Rat Software
http://www.rat-software.com/
Please leave quoted text in place when replying
|
Not Categorized, Please Help
|
|
