From: Richard Cornford on 21 Oct 2009 21:20
> Richard Cornford wrote:
>> The relevance of the internal Reference type to argument
>> passing is questionable anyway as the evaluation of Argument
>> Lists (Section 11.2.4) has the internal GetValue (8.7.1)
>> function called on all the AssignmentExpressions in the
>> list, and while the argument to the GetValue method may
>> or may not be a Reference type the result of that
>> function call cannot ever be one.
> The function argument creation process is rather straightforward
> yet might be far from an obvious one: on call the function gets
> the name of the entry from the name table but doesn't use it
> and it creates two new name table entries instead: ...
> Closure lovers (== "encapsulation is the must that rulez")
> oftenly forget about it so letting their closures'-heavy
> code to leak over the anonymous counterparts.
You are gibbering again. If you don't go back to taking your medicine
you are going to find yourself locked up again for the next six months.
From: VK on 21 Oct 2009 22:06
Richard Cornford wrote:
> You are gibbering again. If you don't go back to taking your medicine
> you are going to find yourself locked up again for the next six months.
If talking about medicine tools you may consider some memory
improvement stuff for your ming as well as obviously some very recent
situations are leaving it way too quickly.
"Function declaration inside other function Options"
the whole thread:
From: Thomas 'PointedEars' Lahn on 22 Oct 2009 05:16
> Thomas 'PointedEars' Lahn wrote:
>> Jorge wrote:
>> > Thomas 'PointedEars' Lahn wrote:
>> >> Johannes Baagoe wrote:
>> >> > According to the tutorial at
>> >> > Object parameters, e.g. objects, arrays and regular expressions,
>> >> > are passed to functions by reference
>> >> That is wrong. Someone competent should use the Wiki functionality of
>> >> MDC and correct it ASAP.
>> > That's not wrong it's perfectly right
>> No, it is not right; apparently you have not been paying attention to
>> what I said. (My posting consisted of much more than what you quoted.)
>> "Pass by reference" has a specific meaning in programming that does not
>> apply here. "Pass by reference" means that a pointer to a memory
>> location is passed so that the data at this memory location can be
>> directly modified, e.g. overwritten with new data, when using this
> No Pointy no.
You have not yet earned the right to be this familiar with me.
> Passed by reference means that you pass a reference: no
> more, no less.
And it does not apply here because "reference" has a specific meaning
attached in general programming and so in the term "pass by reference".
> More specifically, it means that what gets passed is not a copy of a
> certain data (whatever the type of the data), but a reference to it.
> It does not imply anything else, as you're pretending.
And a reference as understood in "pass by reference" is implemented as a
pointer to a memory location. A reference as understood in ECMAScript
implementations is a reference to an object (necessarily stored at a memory
location, but that is beside the point).
As the graph showed, there can be any number of references to the same
object; in this case, both `bar' and the initial value of a refer to the
same object. If anything is copied here at all, it is the reference value.
>> (... miss-the-point nonsense removed ...)
Well, let us assume for a brief moment that you would be right, that I would
have missed the point, and that objects would be passed by reference in
ECMAScript implementations. How do you explain then that any assignment to
the argument named `a' does not modify the object "passed by reference" in
the test case?
var bugRiddenCrashPronePieceOfJunk = (
navigator.userAgent.indexOf('MSIE 5') != -1
&& navigator.userAgent.indexOf('Mac') != -1
) // Plone, register_function.js:16
From: Thomas 'PointedEars' Lahn on 22 Oct 2009 06:24
Johannes Baagoe wrote:
> Thomas 'PointedEars' Lahn :
>> Someone competent should use the Wiki functionality of MDC and correct
>> it ASAP.
> I see you did it. Much better than the previous version, thank you.
You're welcome. However, there is still a lot of other (maybe Resig
induced) nonsense like "function operator" that needs attention from
professionals. I would like to ask anyone knowledgable who thinks
they are good at explaining to novices to do a peer review.
Maybe we can even discuss it here? MDC being a primary reference to the
languages discussed here, I think it would be a good idea if the knowledge
accumulated here would positively reflect back on it. It would also make a
better extension of the FAQ then, which should primarily deal with answers
to *F*requently *A*sked *Q*uestions instead.
realism: HTML 4.01 Strict
evangelism: XHTML 1.0 Strict
madness: XHTML 1.1 as application/xhtml+xml
-- Bjoern Hoehrmann
From: Richard Cornford on 22 Oct 2009 15:18
> Richard Cornford wrote:
>> You are gibbering again. If you don't go back to taking your
>> medicine you are going to find yourself locked up again for
>> the next six months.
> If talking about medicine tools you may consider some memory
> improvement stuff for your ming as well as obviously some
> very recent situations are leaving it way too quickly.
> "Function declaration inside other function Options"
> the whole thread:
If you want to flaunt you notion of 'winning' an argument why
don't you direct people to the thread where you established your
arrays* on the planet"?