--
On Thu, Sep 22, 2005 at 05:47:31AM -0600, Cory Spencer wrote:
>
> >I'm closing this bug as 'rejected' because a corrected patch was never
> >submitted. If you ever get it work, please do resubmit it.
>
> Actually, I believe it was eventually applied, although I'm not sure why
> it wasn't upd
I'm closing this bug as 'rejected' because a corrected patch was never
submitted. If you ever get it work, please do resubmit it.
Actually, I believe it was eventually applied, although I'm not sure why
it wasn't updated in the RT. In any event, two peek opcodes currently
exist in the tree
At 12:00 AM + 1/1/04, Cory Spencer (via RT) wrote:
# New Ticket Created by Cory Spencer
# Please include the string: [perl #25265]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=25265 >
'peek' implements an opcode which c
> > 'peek' implements an opcode which can look ahead at an arbitrary number of
> > bytes in a IO stream, but does not remove the bytes from the stream in the
> > process.
> >
> [...]
>
> I have some question though:
>
> - what if peek wants to look beyond current buffered limits
Yes - at presen
Cory Spencer <[EMAIL PROTECTED]> wrote:
> 'peek' implements an opcode which can look ahead at an arbitrary number of
> bytes in a IO stream, but does not remove the bytes from the stream in the
> process.
> The proposed format is:
> peek(out STR, in INT)
> where $1 contains up to $2 peek'ed by
# New Ticket Created by Cory Spencer
# Please include the string: [perl #25265]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=25265 >
'peek' implements an opcode which can look ahead at an arbitrary number of
bytes in a I
