Beefy Boxes and Bandwidth Generously Provided by pair Networks Cowboy Neal with Hat
laziness, impatience, and hubris
 
PerlMonks  

Re: A few questions regarding Expect.pm and possible alternatives

by 5mi11er (Deacon)
on May 23, 2013 at 20:37 UTC ( #1035020=note: print w/ replies, xml ) Need Help??


in reply to A few questions regarding Expect.pm and possible alternatives

I would recommend you use the expect methods for most everything. Switching back and forth, wondering which method would be better means that it will become more difficult down the road to tweak things to add a smidgen more functionality if you didn't start out using expect for that task.

Expect is pretty mature, as such, there isn't a need to add features all the time, and there are apparently not many bugs that need squashed, so it's age could be considered a good thing. It works, and works well.

Update: (I didn't answer other questions)

If the expect script parts are complicated enough, you might find that writing actual expect scripts rather than embedding them in perl, and calling those scripts from perl may simplify the tasks. This is typically what I've done with my scripts. Without actual or simulated examples, it's difficult to point you in a direction or suggest improvements.

-Scott


Comment on Re: A few questions regarding Expect.pm and possible alternatives

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1035020]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (14)
As of 2014-04-24 12:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (565 votes), past polls