From: sjack@dontemail.me   
      
   Had some notes from long back for building QUAN and VECT using DOES>   
   exploits from examples in Baranoff papers (no surviving link). Apparently   
   the Forth I had then had the same type of CREATE DOES> that with   
   DOES> exploits could produce words with multiple CFAs.   
   I decided to do the same in TOAD, a FigForth derivative, which   
    have CFA followed by a vector. The result was   
   words with multiple vectors and helpers that used ENTER instead of   
   EXECUTE. But then I found QUAN could be easily built without   
   exploits. It reduced to a simple VALUE with the same TO but only   
   without any type checks (could be added). However, I think the point   
   of the Baranoff papers was not so much about what it takes to build   
   QUAN but how DOES> exploits work and how they might be used which   
   I did find informative and interesting.   
      
   In a nut shell, DOES> exploits add small words that begin with DOES>   
   followed by a small silver of code:   
        : FOO does> ... ;   
   When executed in a defining word, they  provide alternate execution   
   paths available for helper words (these paths are not compiled into the   
   the defining words but are taken from these exploit words directly).   
   Also, the defining word has access to the defined word's CFA therefore   
   a link to the defined word's data field address, DFA , if needed.   
      
   Those DOES> exploit words remind me of mRNA bringing in component material   
   for functioning of the DNA in building proteins (which used to be   
   a good thing).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)