On 2/13/06, Tim Bunce <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 13, 2006 at 02:03:22PM -0800, Ben Tilly wrote:
> > What $VERSION was this implemented at?
>
> I didn't say it was for sure. Just that I intended it and thought it was.
> Now I look at the code I see it's not:
> /* XXX need to su
On Mon, Feb 13, 2006 at 02:03:22PM -0800, Ben Tilly wrote:
> What $VERSION was this implemented at?
I didn't say it was for sure. Just that I intended it and thought it was.
Now I look at the code I see it's not:
/* XXX need to support file being a filehandle object */
I'll get to it at s
What $VERSION was this implemented at?
I just tried it on a machine at $VERSION 1.48 and it didn't work. :-(
(This with a filehandle pointing at a pipe, I was going to try a tied
filehandle if that worked.)
Thanks,
Ben
On 2/11/06, Tim Bunce <[EMAIL PROTECTED]> wrote:
> I think $h->trace($level,
That would be perfect. I will attempt that on Monday.
If it works but I can't use a tied filehandle, that's still OK. I'll
just open a pipe.
Thanks,
Ben
On 2/11/06, Tim Bunce <[EMAIL PROTECTED]> wrote:
> I think $h->trace($level, $filehandle) works now so I think you can
> used a tied filehand
I think $h->trace($level, $filehandle) works now so I think you can
used a tied filehandle - certainly that's my intention.
Then the PRINT method of your tied filehandle class can do whatever you
want.
Tim.
On Fri, Feb 10, 2006 at 08:55:30PM -0800, Ben Tilly wrote:
> Is there any easy way of ref
Is there any easy way of reformatting trace information?
I'd like a trace exactly like what DBI->trace(2) creates, except that
I'd like the timestamp (as precise as possible) and pid (ie $$) to be
included in the trace.
So far the best solution that I can think of is to create a named pipe
per pr
