1. .e files included in 300 statement limit
Hi everyone,
I have vague recollections of this being gone over before, but I need to
know: are routines in external include files (.e) counted in the 300
statement limit incurred by the pd version of Euphoria?
If I had 1 procedure defined in my .ex file, but had 50 in the .e file,
would only the statements in the .ex file be counted?
The Euphoria documentation that came with 2.0 says:
"For programs up to 300 statements in size you will enjoy the full
support of Euphoria's excellent debugging facilities. Blank-lines
and comments are not counted, and the standard include files are
free (if not bound or "shrouded")."
Does that mean that the program will still run if it exceeds 300
statements, just without debugging; or will it not run at all?
Thanks everyone :)
----->Buddy
budmeister1 at juno.com
_____________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]
2. Re: .e files included in 300 statement limit
The way I understand it, statements in ".e" files are counted also, except
for those ".e" files that accompany Euphoria when it is downloaded. (I'm not
sure what will happen if one uses modified ".e" files with the standard
names, but I guess Robert thought of this.) The public domain version of
Euphoria will run programs any size, but will not give debug information if
the program crashes. Not exactly a bad deal, I think.
Einar Mogen
3. .e files included in 300 statement limit
RE: Statement Count
Statements in the .e files that come with Euphoria do not count against t=
he
300 "limit". Statements in other .e files (ones you dl or create) do
count. Any program under 300 lines (does that include 300 exactly?) will=
run and you will have the full debugging support. Any program over the
threshhold WILL STILL RUN, but you will have a much more difficult time
debugging. I particularly like the variable value dumps. (I haven't
really written programs over 300 lines, though I've used 3rd party includ=
e
files.)
--Alan
=
