AL>> However, given the low volume of netmail that MakeNL produces, it   
    AL>> seems that it would be a lot of coding, testing, and debugging   
    AL>> time that perhaps could be better spent elsewhere.   
      
    ac>> It'd be easier if MakeNL just called an external program, eg.   
    ac>> MsgPost or PostMsg (etc.)   
      
    ml> bah... just let it create PKTs directly and then the tosser can toss   
    ml> them whichever way they need to go :P   
      
    ac> Presumably this was written in jest, but in case it wasn't, this is   
    ac> a terrible idea.   
      
   in jest? kinda yeah... kinda no... it would be no different than any of the   
   message posting tools that write directly to PKTs which are placed in a   
   special directory for the tosser to toss... why include another program in the   
   flow when the one can just do it itself? ;)   
      
   for that matter, why have makenl call an external program when the script   
   executing makenl can do that if the output file from makenl exists and has   
   been updated? ;)   
      
   i mean, if we're gonna go all *nixy and "do one job and only one job and do it   
   well" style :)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)