expectperl-discuss

Re: [Expectperl-discuss] No match,

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

> I don't like deleting the anchoring to the beginning of the line, 
> since it might get an accidental match with comments or other 
arbitrary
> strings in the router's config.

Then how about anchoring it to the end of buffer ("\Z")?  The prompt 
should be the *last* output, right?

> > Have you set $exp->match_max?
> 
> My script by default sets it to 256k, and the user can specify it
> on the command line.  And if I was overrunning the accumulator,
> wouldn't I just lose the beginning of the data I want rather than
> not match the end?

Right, this was just a hunch.

> Hopefully a few more people will start using the script and I'll
> get some more feedback.  Very strange...

I had another report that the new Expect version suddenly doesn't match 
something that an old version matched.  I'm waiting for additional data 
and will keep you (well, the mailing list) posted.

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

Re: [Expectperl-discuss] No match,

[Ed R. <er...@pa...>]

RGi...@a1... writes:
[eravin wrote]
> > I don't like deleting the anchoring to the beginning of the line, 
> > since it might get an accidental match with comments or other 
> arbitrary
> > strings in the router's config.
> 
> Then how about anchoring it to the end of buffer ("\Z")?  The prompt 
> should be the *last* output, right?

It should be, but there's the pathological case where
there's the accidental match exists *AND* that pattern happens to show
up at the end of a packet *AND* there's a delay before the next
packet.  In which case, the pattern would be at the end of the
accumulator and expect() would be fooled.  Not a very likely case,
but it could still happen (and most certainly WILL happen if I
used \Z that way, probably three times a day :-).

But thanks for the reminder about \Z, I had forgotten about it.

	-- Ed