Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!NISC.SRI.COM!cwilson
From: cwilson@NISC.SRI.COM (Chan Wilson [Animal])
Newsgroups: comp.lang.perl
Subject: Re: Expect.pl, alpha release
Message-ID: <23042@fs2.NISC.SRI.COM>
Date: 3 Nov 90 01:55:38 GMT
References: <1990Nov2.003228.22744@iwarp.intel.com> <7749@muffin.cme.nist.gov>
Organization: Network Info Systems Ctr., SRI Intl., Menlo Park, CA.
Lines: 41

libes@cme.nist.gov (Don Libes) writes:

>In article <1990Nov2.003228.22744@iwarp.intel.com> merlyn@iwarp.intel.com (Randal Schwartz) writes:

OOoh OOh OOh OOh!!!!

Yes yes yes!!

:)

Ever since I came across expect, I've been nashing my teeth over the
fact that it's got such a bizarre, lispy-like syntax, among other,
trivial reasons.  Granted, I'm not much for high-level languages, but
I'd just gotten into perl and was wonderfully spoiled by all the lovely
capabilities with it.  

I was even at the point of trying to emulate expect in perl by 
doing a open(PROC,"|process > /tmp/output") and feed the PROC 
by examining the /tmp/output file.  Never did get beyond the
contemplation stage, thou..

[...]
>In the approach you took, the user language IS Perl, which provides
>incredible power and flexibility.  The primary disadvantage is that
>the user may have to learn Perl, which is hard.

Oooh, Nosh.  I've found that Perl is giving me the same feeling that
BASIC did way back when.  The power, the flexability, the >simplicity<
of the language has won it a permanent place in my language library.

But, I've come from an unusual computer background, so perhaps it's
just me.  :-)

Oh boy!!  Time to convert my expect scripts to perl-expect scripts!!

--Chan

Chan Wilson                                  Chief Hard-Question Answer Person
SRI Intl. Network Information Systems Center
333 Ravenswood Ave., EJ287			Internet: cwilson@nisc.sri.com
Menlo Park, CA., 94025				Phone: (415)859-4492
    "If I want to be a surfer this month, I bloody well will be."