Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 23 OCT 2011 11:16:33PM Johan Liebenberg wrote:

Hi everybody,

I came across this in one of our programs:

"Expendable Subroutine abc(a)"

I believe it comes from Arev days, but I cannot find anything in the OI help documents. Can somebody please enlighten me to the use of this? It compiles OK but is it still of any benefit?

Thanks

Johan


At 24 OCT 2011 08:36AM andrew mcauley wrote:

Hi everybody,

I came across this in one of our programs:

"Expendable Subroutine abc(a)"

I believe it comes from Arev days, but I cannot find anything in the OI help documents. Can somebody please enlighten me to the use of this? It compiles OK but is it still of any benefit?

Thanks

Johan

Expendable was a keyboard which instructed RTP27 to remove the object code from the program stack after execution. This was done for two reasons :-

[list]

to save string space when memory was limited

to ensure that the current version of the code was in use

[/list]

So it was used a lot during development to ensure that a cached version of the code was not called.

It is ignored in OI and has no effect. If you wish to reload object code in OI you can

run rtp27 programName

from the system monitor.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 24 OCT 2011 09:38AM andrew mcauley wrote:

Keyword not keyboard. I'd like to blame predictive text. Regretfully I'll just have to accept stupidity :)

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft


At 24 OCT 2011 04:40PM Johan Liebenberg wrote:

Thanks Andrew!

ps. I didn't even notice the keyboard bit until you pointed it out. Funny how the brain ( or lack there off ) works. :smile:


At 26 OCT 2011 08:44PM Richard Hunt wrote:

Wouldn't the use of the GARBAGECOLLECT statement work? Although it would wipe all cached object code. Works for me.


At 26 OCT 2011 08:52PM Johan Liebenberg wrote:

The code originally came from AREV days. Way back then, CPU cycles and memory was scarce. Now it only interferes with our version control system which didn't know what to do with it. Easy solution was to just delete it. We still have garbagecollect and flush in a few places, but I doubt if we even need that.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/cad987610004915054b17ea00.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1