Last I checked there were a number of crappy Perl
wrappers around Libes' Expect. That was the situation with
Python too before I wrote Pexpect. I think the problem is
also harder in Perl because I don't think they have a standard
pty module -- although I may be wrong now since I don't really
keep up on the Perl libraries any more ;-) I would not have
written Pexpect if it were not for the standard Python pty module.

I too, admire autoexpect. Of course, it never actually produced
a working script for me, but it was great for getting started.
I thought of trying to do an autoPexpect, but currently I have not enough
time to even work on Pexpect. Although Pexpect is almost "done",
there are still a few little things I need to work on. I also want
to submit it to be part of the Standard Library... I think that
Pexpect is good enough now that one could write autoPexpect
using the pexpect module. On the other hand, half the reason
I used Autoexpect to get started was because I could
never remember how to write an Expect script.

Yours,
Noah

----- Original Message -----

> I use to script interaction with modem pools and routers in expect
> when I worked for an isp.  Autoexpect kicked butt, it captured your
> manual interactions then you'd just go into the generated script and
> generalize things stripping timestamp responses and such that would
> trip up subsequent runs.  
>
> Hmm so this is expect redone in python, which is good because tcl
> doesn't really have a huge following.  Not that I have anything
> against python but is there another in perl? ;-)  
>
> --
> Ted Guild <[email protected]>
> http://www.guilds.net
>