expectperl-discuss

Re: [Expectperl-discuss] several sequental spawns

[<RGi...@a1...>]

> It looks like perl-Expect doesn't support for several subsequent 
> spawns for on objects

Right, I never checked if this works, so it doesn't. :-)
 
> I got a message here in logs telling that /dev/pts/7 which was 
> used for the first program interaction doesn't exist anymore
> (no such file or directory)

This probably comes from the pty that is closed but not completely 
destroyed.

> If I replace the second $expect->spawn with Expect->spawn the program
> works Ok.

Because then you are creating a new object.

> Is there a way to skip creation of another Expect object, or
> at least cloning settings from the first object to the second one?

Sorry, no, not at the moment.  I'll add this to the 'to do' list...

Thanks for the suggestion!

Roland
--
RGi...@cp...

Re: [Expectperl-discuss] several sequental spawns

[<RGi...@a1...>]

> > sounds reasonable. May be it's time to add a 'clone' function to 
> > Expect? All 'shareable' settings are to be copied inside the 
> > func, and unique ones get re-created... Unfortunately I know
> > too little about an Expect's object insides for the moment
> > and probably can't say exactly whether 'clone' should allocate
> > a new pty for each new instance etc... 
> 
> 	I think you would have to. So, the purpose of the clone would be
> to do something like spawn a process using the same parameters? I 
> guess I'm not seeing much benefit over setting the default
> parameters using packagevariables, e.g. $Expect::Exp_Internal.
> Maybe I don't understand the concept of 'clone' well enough.
> 	Also, how would it apply to filehandles expectified using 
> exp_init?

Don't forget that an Expect object is basically a filehandle, and the 
semantics of cloning a filehandle are vague, to say the least.  Should 
the filehandle be connected to the same file/process?  Should we reuse 
the pty?  Copy the tty settings?  Or just the Expect-specific 
parameters?  I don't see a clear, easy DWIM-solution for this, so I 
wouldn't poke deeper into this snake-pit...

But what I could add is a check that prohibits spawning another process 
with an already-used object to avoid such misunderstandings.  And of 
course amend the docs...

Roland
--
RGi...@cp...

Re: [Expectperl-discuss] several sequental spawns

[Alexey M. <mo...@no...>]

=F7 =F7=D4=D2, 19.03.2002, =D7 15:56, RGi...@a1... =CE=C1=D0=C9=D3=C1=CC=
:
> Don't forget that an Expect object is basically a filehandle, and the=20
> semantics of cloning a filehandle are vague, to say the least.  Should=20
> the filehandle be connected to the same file/process?  Should we reuse=20
> the pty?  Copy the tty settings?  Or just the Expect-specific=20
> parameters?  I don't see a clear, easy DWIM-solution for this, so I=20
> wouldn't poke deeper into this snake-pit...
Ok, I see, probably 'clone' is a bad idea... I just didn't count all
possible problems in design and implementation before asking for it...

> But what I could add is a check that prohibits spawning another process=20
> with an already-used object to avoid such misunderstandings.  And of=20
> course amend the docs...
Ok, it would be enough for a newbie like me :-)

Thank you.

Alexey Morozov.