On Mon, Feb 05, 2001 at 11:15:41PM -0500, Dan Sugalski wrote:
> This isn't really what I'd consider a good thing, but raw memory access in
> perl would be convenient. There'll probably be a special type of reference
> that lets you do that. (Only needs a few changes to the vtable code, too)
It'
At 06:35 PM 2/5/2001 -0600, David L. Nicol wrote:
>Are we willing to let user-code use codereftagstrings abckwards yet?
Yes, we are.
>We would gain C style casting capability, with all the evil that brings
>with it, including the ability to bittwiddle perl structures from
>within perl, which is
At 06:35 PM 2/5/01 -0600, David L. Nicol wrote:
>--- warning --- bad idea follows ---
You're not kidding.
>Are we willing to let user-code use codereftagstrings abckwards yet?
>
>perl -le '$a = \(1..4); $tagstring="$a"; print @{$tagstring}'
>
>We would eliminate all strings matching /^[A-Z]\(0x
Dan Sugalski wrote:
> >IMO the name of the currently executing sub should be accessed via an
> >extention to C.
> >
> > caller{subname}
>
> Oh? What prints, then?
>
>$foo = sub {print caller{subname}};
>$foo->();
something like CODE(0x80cfd7c) since we don't have a better name
At 04:59 PM 2/5/2001 -0600, David L. Nicol wrote:
>James Mastros wrote:
>
> > > At least it's independent of the sub's name. I wish this could be
> > > extended to doing recursive calls without having to say the subs own
> > > name, again.
> > I agree, making the magic variable be the name of the
