Re: Need help debuggin
> Good Morning Everyone,
> 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. 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.
> 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
>
> -Dan
You could use an older version of Win32Lib that's been stamped, this
means it doesn't count towards the 300-line limit. I think the last
version to be stamped was David Cuny's last solo release, this is
quite out of date now but you can still get it from the archives at:
It is quite possible to debug a 300 plus line program without the full
version (although it's still very nice to have:) use the ? statement
or the puts procedure to output markers, for example:
puts(1,"Declaring variables...\n") --DEBUG
atom a,b,c
puts(1,"Assigning values...\n") --DEBUG
a=0
b=1
puts(1,"Divding b by a..\n") --DEBUG
c=b/a --This will cause an error
puts(1,"All done!") --DEBUG
When tracing you can skip a procedure by pressing the down arrow
rather than enter, this way you don't need to trace into bits of code
you didn't write. Also you can put the "with trace" after the "include
win32lib.ew", this will stop it traceing into win32lib code.
Good luck with it :)
Thomas Parslow (PatRat) ICQ #:26359483
Rat Software
http://www.rat-software.com/
Please leave quoted text in place when replying
|
Not Categorized, Please Help
|
|
