You're right, EXECIO does not use stem.0 for DISKW; I had misremembered that. On the other hand, mainframe EXECIO stops writing when it encounters a stem element whose value is unset or is the empty string; ooRexx EXECIO does not do this.
Leslie On Monday 19 August 2013 20:45:42 Chip Davis wrote: > David is correct about the .0 tail of a stem: it's no different from > any other tail, except that EXECIO uses it (for DISKR operations only) > as a place to stash the number of the highest tail it created. > > EXECIO does not pay any attention to it for DISKW, probably because it > doesn't trust us to have scrupulously maintained its value, as you > seem to have. > > That does not mean that you can't use stem.0 for that purpose when > writing out your array, however. > > 'EXECIO' stem.0 'DISKW' outfile '(STEM MYSTEM. FINIS' > > for example. Of course, MYSTEM. must still be monotonic (i.e. not > sparse, with gaps in the index) for this to work correctly. > > -Chip- > > On 8/19/2013 09:01 David Ashley said: > > The remove method does not know about or care about the contents of > > stem.0. Using stem.0 as a counter for the number of items in a stem > > variable is a programming convention and has nothing to do with the way > > stems work. The remove method simply invalidates the tail reference and > > does NOT modify the stem.0 value. > > > > David Ashley > > ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
