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 sub is a bad idea. > > Your idea for a name for the currently executing sub is interesting, I > think. I'm going to fork the thread. > > -=- James Mastros IMO the name of the currently executing sub should be accessed via an extention to C<caller()>. caller{subname} For that matter a reference to the lvalue if any could be caller{lvalue} instead of another LNV.
- Re: assign to magic name-of-function variable instead of &q... Peter Scott
- Re: assign to magic name-of-function variable instead of &q... David L. Nicol
- Re: assign to magic name-of-function variable instead ... James Mastros
- Re: assign to magic name-of-function variable inst... Johan Vromans
- Re: assign to magic name-of-function variable ... James Mastros
- Re: assign to magic name-of-function varia... Bart Lateur
- Re: assign to magic name-of-function ... James Mastros
- Re: assign to magic name-of-funct... abigail
- Re: assign to magic name-of-funct... James Mastros
- Re: assign to magic name-of-funct... Branden
- Re: a name for the currently exec... David L. Nicol
- Re: a name for the currently exec... Dan Sugalski
- Re: a name for the currently exec... David L. Nicol
- Re: a name for the currently exec... Peter Scott
- Re: a name for the currently exec... Dan Sugalski
- Re: a name for the currently exec... Nicholas Clark
- Re: assign to magic name-of-function ... James Mastros
- Re: assign to magic name-of-function varia... John Porter
- Re: assign to magic name-of-function variable instead ... John Porter
- Re: assign to magic name-of-function variable inst... David L. Nicol
- Re: assign to magic name-of-function variable ... James Mastros