|and dont forget the GTO [.][.]|
Message #3 Posted by Vieira, Luiz C. (Brazil) on 3 Mar 2003, 11:54 a.m.,
in response to message #2 by Mike (Stgt)
I read Jeff's post and wondered about it. I read yours and I think I did not understand the doubt.
Is there a way to "compile" a program, i.e., to compute and record the distances from GTO's and XEQ's to their respective LBL's and keep this information? I know taht if you execute a [GTO][.][.] and the program is packed as a consequence of it, all of this information is erased. If the program already has an END as the last instruction (say, if you put it there manualy with a [XEQ][ALPHA] END [ALPHA] instead of a [GTO][.][.]) and you execute it, all EXECUTED GTO's and LBL's are compiled. But if you pack memory for any reason, this information is lost.
My doubt goes further when I think of those GTO's or XEQ's that are executed only in certain conditions and these conditions are not reached when running the program. Two questions:
- it seems that 'LBX' program mentioned by Jeff will compile thess not-executed jumps, what is an important fact, indeed
- manualy positioning the calculator on each not-executed GTO or XEQ and executing a single [SST] in RUN mode would also compile that specific GTO or XEQ? I think it will, but I'd like to know if it is a fact or a simple guess.
I would like to know more about the fact a PRIVATE program is not decompiled. Even if it is read form a card or X-Memory? I was not aware about that... Interesting!
All of the compilation process is lost when a program is changed or recorded somewhere and brought back to main memory, say, if it stays in main memory and it's unchanged, the compilation data is kept untouched. Or if it is recorded in ROM'what demands the compilation of all GTO's and XEQ's, isn't it?
Luiz C. Vieira - Brazil