On Feb 28, 10:32 am, Nathan Sweet wrote:
> Rob,
> I'm obviously not being clear enough.
> >There is no declaration, only assignment. And it can be done anytime
> >before the function is called, you can declare the function then
> >assign the modified version later if you want.
>
> Why does the m
On Feb 28, 10:39 am, "Ionuț G. Stan" wrote:
> On February 28, 2011 1:59 AM, RobG wrote:
>
> >> This isn't the interesting thing yet. What is interesting about this
> >> function is how it is invoked.
>
> > You mean called.
>
> What's the difference? You're obviously pedantic, but I'd like to kno
On Feb 28, 8:52 am, Julian Turner wrote:
[...]
> 1. Inheritance in JavaScript is implemented through chains of
> prototype objects, ending ultimately at Object.prototype.
Strictly, it ends with the object referenced by the internal
[[prototype]] property of Object.prototype, which is null.
>
On February 28, 2011 1:59 AM, RobG wrote:
This isn't the interesting thing yet. What is interesting about this
function is how it is invoked.
You mean called.
What's the difference? You're obviously pedantic, but I'd like to know
the exact difference that you were thinking about.
--
Ionuț
Julian,
Thanks for the reply. Let me add some clarifications/questions that I didn't
offer before.
1. I don't know quite what you mean in item 3 of your argument when you say:
>If you seek to access the method "overloadSetter" on a function,
>under point 1 above, the interpreter will eventually fi
On Feb 28, 5:29 am, nathanJsweet wrote:
> I've got a really interesting javascript pattern that I've been
> scratching my head over for a while. I basically understand what is
> going on with what I'm about to talk about, but I would like a fuller
> explanation than what I've been able to find on
On Feb 27, 7:29 pm, nathanJsweet wrote:
> I've got a really interesting javascript pattern that I've been
> scratching my head over for a while. I basically understand what is
> going on with what I'm about to talk about, but I would like a fuller
> explanation than what I've been able to find o
I've got a really interesting javascript pattern that I've been
scratching my head over for a while. I basically understand what is
going on with what I'm about to talk about, but I would like a fuller
explanation than what I've been able to find on my own. Method
invocation at declaration:
On Fri, Feb 25, 2011 at 6:14 PM, mcot wrote:
> I have some sample code below that generates a different result
> between browsers. I *think* chrome is doing the wrong thing, but I
> wanted to ask here first.
>
>
>function func(param) {
>console.log(param.x)
>
