Re: Perl threads in Object Oriented code
- From: xhoster@xxxxxxxxx
- Date: 01 May 2007 15:50:49 GMT
Eric <ecarlson@xxxxxxxxxx> wrote:
xhoster@xxxxxxxxx wrote:
Someone made a similar suggestion, but it seems as if you are
redefining the sub in the file in which it is being called instead of
using it from it's current module(?).
sub{...} creates a new anonymous sub. It can't redefine any existing
subs because to do that, you would need to use the name (or a ref to)
an existing sub, which being anonymous this ones doesn't have.
Xho
Ok - I can see the rationale behind this. In fact, I tried it, and it
worked. However, I got the oddest response message I've ever seen:
Attempt to free unreferenced scalar: SV 0xafc2db8, Perl interpreter:
0xaa069a0 at <file> <line>
What version of Perl are you using? I've seen things like that in
some of the early 5.8.x perls that went away in the some of the later
ones.
Xho
--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB
.
- Follow-Ups:
- Re: Perl threads in Object Oriented code
- From: Eric
- Re: Perl threads in Object Oriented code
- References:
- Re: Perl threads in Object Oriented code
- From: xhoster
- Re: Perl threads in Object Oriented code
- From: Eric
- Re: Perl threads in Object Oriented code
- Prev by Date: Access hash of hashes element problem.
- Next by Date: using split to extract characters
- Previous by thread: Re: Perl threads in Object Oriented code
- Next by thread: Re: Perl threads in Object Oriented code
- Index(es):
Relevant Pages
|