Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!uflorida!bikini!thoth From: thoth@reef.cis.ufl.edu (Robert Forsman) Newsgroups: comp.lang.perl Subject: Re: Merged Tcl and Perl? Message-ID: Date: 9 Apr 91 05:33:36 GMT References: <21782@shlump.nac.dec.com> <1991Apr6.143307@sic.epfl.ch> Sender: news@uflorida.cis.ufl.EDU Organization: Zik Zak Lines: 18 In-reply-to: brossard@sic.epfl.ch's message of 6 Apr 91 12:33:07 GMT Around here I use Tk as a wrapper for messy commands like enscript (part of the TransScript package). Anything that has a lot of arguments that a clueless user can't figure out in 5 seconds is a target and gets turned into a button encrusted window. I often have to use awk and sed to do parsing, and I really wish I had the power of regexps and IO in tcl. I also use it to write empire toys, but that's another story. The idea of giving perl access to tcl interpreter capability is nifty, but I wonder if we can stop at just that. Although, once perl has X capability, what else is there? We also use plain tcl as a quick-and-dirty parser. -- "Rob, you're stupid, and that makes you dangerous." - chess opponent I deal with Reality as you _don't_ understand it. Hammor -= Supreme Commander of the Ice Pirates =-