Traditionally BL WORD places a word from the input stream,   
   (terminal input buffer, stream buffer or file buffer)   
   onto HERE where it can be fetched by $@-BD ( aka COUNT).   
   Even gforth does this, and undoubtedly many legacy programs   
   will crash on gforth, if it does behave otherwise.   
   (Tested on gforth 0.7.3).   
   [The idea was that it is the name of a colon word, and the   
   laborious task of copying it from the input buffer should not   
   be done only once, so the headers were defined such that the name   
   was in the right place. This dates from the seventies of the last   
   century.]   
      
      
   Reading iso93 section 3.3.3.6.   
   A lot of interference can be avoided to define   
   CREATE PAD ALLOT ALIGN   
   A permanent region could serve as a transient region, so   
   from the users of PAD there is no problem.   
   Common sense dictates that the simultaneous use of PAD for conflicting   
   purposes should be avoided, as is the same now.   
      
   In view of Gigabyte memories, a lot of interference could also be   
   avoided, if BL WORD were entitled to ALLOT the space.   
   A permanent region could serve as a transient region, so   
   from the users of WORD there is no problem.   
      
   : WORD WORD DUP COUNT ALLOT ALIGN ; \ Or some such.   
      
   Is this in conflict with the standard?   
      
      
   Groetjes Albert   
   --   
   Temu exploits Christians: (Disclaimer, only 10 apostles)   
   Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall   
   Art For Home, Office And Garden Decor - Perfect For Windows, Bars,   
   And Gifts For Friends Family And Colleagues.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)