In article <66319f99$1@news.ausics.net>, dxf   wrote:   
   >On 1/05/2024 5:09 am, Gerry Jackson wrote:   
   >> On 29/04/2024 21:54, Paul Rubin wrote:   
   >>> Gerry Jackson  writes:   
   >>>> - the pictured output buffer (POB) may be transient, can be corrupted by   
   >>>>    the system e.g. being  moved or overwritten   
   >>>   
   >>> Yeah that's a typical Forthy thing though.  So after calling #> you have   
   >>> to copy the output away before doing anything else that could mess with   
   >>> the POB..   
   >>   
   >> Yes I know, but that shouldn't be necessary. I guess it's a hangover from   
   the time 40 years ago when memory was a scarce and expensive commodity. Things   
   like this should be weeded out of the standard.   
   >   
   >How is efficient use of a resource 'a hangover'?  I've no particular   
   allegiance   
   >to Standard Forth and will happily argue against things that were never   
   properly   
   >considered e.g. the topic of this thread.  Multiple HOLD buffers is like   
   multiple   
   >S" buffers.  For some folks one is never enough.   
   >   
   Multiple buffers is a cludge, more so than a single buffer.   
   The preferred enhancement is using ALLOCATE, enhanced with a string-save   
   mechanism. ( $!a $@a )   
   ALLOCATE packets with a SIZE (Aguilar's invention?) are especially nice.   
      
   Groetjes Albert   
   --   
   Don't praise the day before the evening. One swallow doesn't make spring.   
   You must not say "hey" before you have crossed the bridge. Don't sell the   
   hide of the bear until you shot it. Better one bird in the hand than ten in   
   the air. First gain is a cat purring.            - the Wise from Antrim -   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)