🚀 go-pugleaf

In article <Mar.4.00.37.35.1990.19269@pilot.njin.net> limonce@pilot.njin.net (Tom Limoncelli) writes:
>In article <48f6cbee.db93@edsel.engin.umich.edu> chrisl@caen.engin.umich.edu (Chris Lang) writes:
>> language, is it?  How will Tcl change this...won't one still need to write
>                   ^^^^^^^^^^^^^^^^^^^^^^^^^
>> the code to handle any commands it can receive?  (True, you won't need to
>
>No, you tell Tcl what the token is, where the code for it's handler
>starts, and it does everything.

But you still need to write the handler yo'self, right?  This is what I was
getting at, although in an admittedly unclear fashion.  I realize Tcl will
take care of the parsing and so on for me.  (In other words, we're talking
about the difference between having a startup.o to parse my application's
command line, and having to do it myself, only for scripts, right?)

 -Chris
-----
Chris Lang    University of Michigan, College of Engineering
home: 4622 Bursley             work: National Center for Manufacturing Sciences
      Ann Arbor, MI  48109           900 Victors Way, Suite 226
      (313) 763-1832                 Ann Arbor, MI  48108
chrisl@caen.engin.umich.edu          (313) 995-0300
"I hate quotations.  Tell me what you know."  - Ralph Waldo Emerson