OpenEuphoria

Re: Need help debuggin

• Posted by leviathan at uswest.net Mar 04, 2001
• 411 views

> Good Morning Everyone,

Heya Dan!


>     I am fairly new to programming in Euphoria, but for the most part it is 
> very user friendly.  I have just started to program in windows instead of 
> DOS because it appears to be much easier.

IMHO, Dan, I can say it is easier, but the trace in a console is a 
pain in the butt to work with (updates very slowly) :)

I, myself, haven't started really doing any programs in Euphoria, 
aside my try to make a card database out of RDS' Guru, and some 
other failed project I can't remember, until about September, when 
automagically I finally understood the language. (Haven't mastered it 
yet, but it shouldn't be too long) Maybe it's because of that beautiful 
lady in my life? Sure :)

> The only problem is that almost 
> with every program I run I get the "Your program exceeds 300 statements in 
> size and cannot provide run-time diagnostics."  I know that I can fix this 
> by registering but I am only 14 and don't really have that kind of money at 
> hand.  Plus I'm really, really cheap.

Give it time, Dan, and you will. You'll have the money sometime :)

Trust me, I'm gonna be on my way to registering the interpreter and 
Eu2C sometime here :)

Altho Rob, if I do, and you release something suddenly on me, I'm 
gonna telepathically poke your brain for doing it to me, because I'd 
have to pay for the update so soon too :)

>     Is there another way to check out my programs when their not working?  I 
> know there is trace but it traces some program that I have never seen 
> before.  Could someone either:
> 1) Tell what exactly trace does & how to use it
>                  or
> 2) Let me know of a different way to debug my programs

I think what you're getting a trace into is Win32lib.ew, which, I'll add, 
does have its 'with trace' statements splattered inside the file. Take 
your favorite editor, and do a massive "find and replace", for "with 
trace", replace it with nothing.

And, to trace well, you have to understand the flow of your program. 
If you see it happening when something happens, like you press a 
button, and something weird that you didn't want happens, obviously 
it's happening right when that button is pressed, in a procedure you 
wrapped the "onClick" to. And then you fix it, abort the program, and 
rerun it! :)

Have fun programming in Windows, Dan! :)

--"LEVIATHAN"