From: address@nospicedham.not.available   
      
   Rick,   
      
   > If you intermix data and code you'll be polluting the instruction cache   
   > with unnecessary data that's not needed.   
      
   You're jumping to conclusions.   
      
   The idea is that the programmer can define the strings where they are used.   
   But there is nothing stopping the implementation from gathering and putting   
   them into a data segment (either per procedure, or even globally).   
      
   Pretty-much the same way how a programmer can define data segments that are   
   in the scope of a procedure (allowing local data labels), but in the end   
   they all get stuffed into a single, big one (witch no slack space/filler   
   bytes in between).   
      
   > Make it look the way you'd like to see it, but then have the tool   
   > translate it to the needs of the machine.   
      
   And that seems to be exactly his goal.  With the "tool" being whatever his   
   assembler already has in regard to a preprocessor and/or macro language.   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)