1. Program overheads
Hi
Not sure if this is a really stupid question, but are there any limits on an eu
program, in terms of number of variables / size of variables / number of
functions / procedures etc?
For instance, I'm writing a program at the moment, which is growing and growing,
and I keep having to add more and more functions / procedures/ variables etc. The
interpreter has to keep track of all of these, so is there a limit to what it can
handle.
There does seem to be a limit to the size of an individual sequence (from what I
can tell true plus virtual memory availability).
If there are limits, is there any way we can test and warn for approach to the
limits?
Chris
http://members.aol.com/chriscrylex/euphoria.htm
http://uboard.proboards32.com/
http://members.aol.com/chriscrylex/EUSQLite/eusql.html
2. Re: Program overheads
Chris Burch wrote:
> Not sure if this is a really stupid question, but are there any limits on an
> eu program, in terms of number of variables / size of variables / number of
> functions / procedures etc?
>
> For instance, I'm writing a program at the moment, which is growing and
> growing,
> and I keep having to add more and more functions / procedures/ variables etc.
> The interpreter has to keep track of all of these, so is there a limit to what
> it can handle.
>
> There does seem to be a limit to the size of an individual sequence (from what
> I can tell true plus virtual memory availability).
>
> If there are limits, is there any way we can test and warn for approach to the
> limits?
For most things, such as the number and size of variables and routines,
there is no hard-coded limit. You will just run out of memory
at some point. Judith's IDE is well over 100,000 lines of code,
and I don't hear complaints about it running out of memory.
2.4 and earlier had a limit on the length of one line of source
(200 characters) but that limit was removed in 2.5, when the
front-end was rewritten in Euphoria instead of C.
There's also a limit on the number of simultaneously open files
(20 or so), but without that limit you'd quickly run into the
operating system limit.
I can't think of any other significant limits off the top of my head.
I don't know of anyone who is being severely constrained by running into
a limit. I suppose there are a few other limits, but they are insanely high.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Program overheads
- Posted by Vincent <darkvincentdude at yahoo.com>
Nov 05, 2005
-
Last edited Nov 06, 2005
Robert Craig wrote:
> There's also a limit on the number of simultaneously open files
> (20 or so), but without that limit you'd quickly run into the
> operating system limit.
You do plan to fix that to 30 for the next release right? Nested includes and
open files are correlated to eachother.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Regards,
Vincent
4. Re: Program overheads
- Posted by Chris Burch <chriscrylex at aol.com>
Nov 05, 2005
-
Last edited Nov 06, 2005
Cheers, interesting to know.
Chris
http://members.aol.com/chriscrylex/euphoria.htm
http://uboard.proboards32.com/
http://members.aol.com/chriscrylex/EUSQLite/eusql.html
5. Re: Program overheads
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 05, 2005
-
Last edited Nov 06, 2005
Vincent wrote:
> Robert Craig wrote:
> > There's also a limit on the number of simultaneously open files
> > (20 or so), but without that limit you'd quickly run into the
> > operating system limit.
>
> You do plan to fix that to 30 for the next release right? Nested includes and
> open files are correlated to eachother.
Yes, I'm going to increase both limits in the next release.
In 2.5, I increased the limit for nested includes to 30
(although no program that I'm aware of ever needed it),
but because the front-end was rewritten in Euphoria, the
Euphoria limit on simultaneously-open files trumped the limit
on nested includes.
Note: I'm talking about the level of *nesting* of includes, *not*
the total number of files you can include in a program.
All include files are closed immediately after the front end finishes
reading them, but with nesting, you may have multiple include files
open at one time. By the time that execution begins, all source files
are closed.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
6. Re: Program overheads
- Posted by Vincent <darkvincentdude at yahoo.com>
Nov 05, 2005
-
Last edited Nov 06, 2005
Robert Craig wrote:
>
> Vincent wrote:
> > Robert Craig wrote:
> > > There's also a limit on the number of simultaneously open files
> > > (20 or so), but without that limit you'd quickly run into the
> > > operating system limit.
> >
> > You do plan to fix that to 30 for the next release right? Nested includes
> > and
> > open files are correlated to eachother.
>
> Yes, I'm going to increase both limits in the next release.
> In 2.5, I increased the limit for nested includes to 30
> (although no program that I'm aware of ever needed it),
> but because the front-end was rewritten in Euphoria, the
> Euphoria limit on simultaneously-open files trumped the limit
> on nested includes.
I was making some test programs for VEEU, and ran into the problem, so I decided
to reported it. I'm sure its very easy to fix.
> Note: I'm talking about the level of *nesting* of includes, *not*
> the total number of files you can include in a program.
Right, I believe the limit is 256 for the total number of files you can include.
You probably wont ever need to increase that limit.
>
> All include files are closed immediately after the front end finishes
> reading them, but with nesting, you may have multiple include files
> open at one time. By the time that execution begins, all source files
> are closed.
If I remember correctly, previous releases did not close the source files until
program termination?
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Regards,
Vincent
7. Re: Program overheads
Vincent wrote:
> If I remember correctly, previous releases did not close the source files
> until
> program termination?
In previous releases the interpreter might execute code
while it was still parsing the source, so some source files
might be open, depending on where you were in the source.
In particular, the main source file would probably be open
at all times.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
