had same thought ... that wouldn't need much explanation neither. +1 here On Thu, Feb 26, 2015 at 11:59 PM, Domenic Denicola <[email protected]> wrote:
> function.current? > ------------------------------ > From: Andrea Giammarchi <[email protected]> > Sent: 2015-02-26 18:56 > To: Tab Atkins Jr. <[email protected]> > Cc: es-discuss <[email protected]> > Subject: Re: Proposal: Additional Meta Properties for ES7 > > agreed ... between `self` and `callee` probably `self` is better. Anyone > with a different/new idea? > > On Thu, Feb 26, 2015 at 11:50 PM, Tab Atkins Jr. <[email protected]> > wrote: > >> On Thu, Feb 26, 2015 at 3:27 PM, Claude Pache <[email protected]> >> wrote: >> > Alternative name for `function.callee`: I find that `function.self` >> sounds >> > better in case of recursive call (and probably in other cases as well). >> >> Agreed that "callee", while technically accurate, is a clumsy word and >> something like "self" sounds better. "function.self", in particular, >> seems to communicate the right semantic, and implies that you're >> receiving a function . >> >> It doesn't feel... apt, I think, to bring the caller/callee >> relationship to mind when you're not trying to deal with that >> relationship; all you're trying to do is recurse on yourself, in the >> case where you don't have a name to refer to yourself with. The fact >> that you're running because someone else called you is irrelevant to >> this dynamic. >> >> ~TJ >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
