On Tue, Apr 20, 2004 at 11:16:07AM +0200, Tassilo von Parseval wrote:
> On Tue, Apr 20, 2004 at 09:18:12AM +0100 Nick Ing-Simmons wrote:
> > Would both give C "foo" calling sharepvn() on that would however look
> > up that string and return a pointer to shared copy.
> >
> > This is used by perl'
On Fri, Apr 23, 2004 at 11:42:50PM +0100 Nicholas Clark wrote:
> On Tue, Apr 20, 2004 at 11:16:07AM +0200, Tassilo von Parseval wrote:
> > On Tue, Apr 20, 2004 at 09:18:12AM +0100 Nick Ing-Simmons wrote:
>
> > > Would both give C "foo" calling sharepvn() on that would however look
> > > up that
On Tue, Apr 20, 2004 at 09:18:12AM +0100 Nick Ing-Simmons wrote:
> Scott T. Hildreth <[EMAIL PROTECTED]> writes:
> >> >
> >> > .. so the address of $fldnm is always the same (static). Therefore the
> >> > fld->names that are sent in all point to the same address. How do I get
> >> > a new SV
Scott T. Hildreth <[EMAIL PROTECTED]> writes:
>Thanks Tassilo! I did not know about savepv, very convenient, like
>strdup. Just curious, is the the SV memory being re-used, or is it
>not going out of scope? I didn't think it would be static.
>
>> >
>> > sub set_name {
>> > my ($self, $fl
Thanks Tassilo! I did not know about savepv, very convenient, like
strdup. Just curious, is the the SV memory being re-used, or is it
not going out of scope? I didn't think it would be static.
On Mon, 2004-04-19 at 12:54, Tassilo von Parseval wrote:
> On Mon, Apr 19, 2004 at 12:08:03PM -05
On Mon, Apr 19, 2004 at 01:20:55PM -0500 Scott T. Hildreth wrote:
> Thanks Tassilo! I did not know about savepv, very convenient, like
> strdup. Just curious, is the the SV memory being re-used, or is it
> not going out of scope? I didn't think it would be static.
It's certainly not static i
On Mon, Apr 19, 2004 at 12:08:03PM -0500 Scott T. Hildreth wrote:
> I have a xsub that has a pointer to a c-structure, and a sv as the
> parameters,
>
> IV
> set_fld_name(fld, name)
>
> FLD * fld
> SV * name
> PREINIT:
> STRLEN len;
> CODE:
> if (name == (SV
