OK, good. BTW, how do you know it's a girl?
I have the Ronco home ultrasound.
Here's a simple demo. Save all five PMs (as five separate files) to
the same directory, then:
RUN 0.PM
There are three ways to that avoid kind of memory load.
1) Don't introduce unnecessary new S/Gs in the parent or child;
rather, reuse -- that is, overwrite the contents of -- existing S/Gs
wherever possible. (This is sound programming technique in any
context.)
That happens pretty much automatically, the way I use XyBasic. It numbers
each variable with the next available S/G number, starting at 01. Since
each program is separately compiled, the daughter programs are overwriting.
2) Don't use child routines; "promote" them to the parent
level and manually issue separate RUN commands for each routine.
I don't understand. What would a "child routine" be?
3) For very large data sets, store the data in one or more editable
files, have the PM CAll the file(s) and operate on (edit) the data
in the document window, then SAve the file.
Yes, I can see that being good. I will have to look at which S/Gs contain
long strings.
Also, remember that program code itself occupies valuable real
estate in the cramped XPL memory space -- a compelling reason to
keep PMs as small as you can, and to avoid using very large child
programs or subroutines. The children continue to take up space as
long as the parent is still working, yet another instance of art
imitating life.
Very witty.
I'm getting VA$M+6 as high as 27 (once I saw 100, but I think that had to
be a mistake how I was storing and displaying memory). 27 is dangerous, right?
Thanks,
Harry
Harry Binswanger
hb@xxxxxxxx