George Schlossnagle <[EMAIL PROTECTED]> writes:
>
>So what I have going on is that I have data I'm passing in and out of
>another language (PHP, specifically), and I'm holding it in either
>opaque types (if it's an object or has discernible magic), or
>converting into a native type. What I h
On Jul 7, 2005, at 9:34 AM, Nicholas Clark wrote:
On Tue, Jul 05, 2005 at 02:24:41PM -0400, George Schlossnagle wrote:
Do you see any other common situations that implementing this might
break? Specifically I'm worried about
having some data come in that looks very much like this, but who
r
On Tue, Jul 05, 2005 at 02:24:41PM -0400, George Schlossnagle wrote:
> Do you see any other common situations that implementing this might
> break? Specifically I'm worried about
> having some data come in that looks very much like this, but who
> really needs to be maintained as an opaque PV
Thanks for your prompt reply. I have a follow-up question, if you
don't mind.
On Jul 5, 2005, at 2:06 PM, Nicholas Clark wrote:
I suspect what has happened is that perl has re-used the same
scalar that
used to have magic. Because perl never (strictly nearly never)
downgrades
scalars, as
On Tue, Jul 05, 2005 at 10:36:58AM -0400, George Schlossnagle wrote:
> I'm working on a rather large XS project, and I have this weird SV
> that I'm seeing:
>
> SV PVMG(0xab0cca0) at 0xab12fd4
> REFCNT = 2
> FLAGS = (TEMP,POK,pPOK)
> IV = 0
> NV = 0
> PV = 0xab0c170 "This is the column
