Path: csiph.com!news.mixmin.net!weretis.net!feeder1.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Thomas 'PointedEars' Lahn Newsgroups: comp.lang.javascript Subject: Re: array-like objects Date: Wed, 06 Jan 2016 19:27:12 +0100 Organization: PointedEars Software (PES) Lines: 84 Message-ID: <5228236.6i9bdH4Rbl@PointedEars.de> References: <39241641.QMrUfM43MS@PointedEars.de> <15615987.a6MfTLryX4@PointedEars.de> <4796632.tdeKqXnCYY@PointedEars.de> <2389107.ZQXF91zPQe@PointedEars.de> Reply-To: Thomas 'PointedEars' Lahn Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Trace: solani.org 1452104832 2821 eJwFwYEBwCAIA7CXCoN2noMo/59gkh+NrWAycnKwf6GWW1exIdlcHawVfU2FBum74Mei5fcBFzkQ5w== (6 Jan 2016 18:27:12 GMT) X-Complaints-To: abuse@news.solani.org NNTP-Posting-Date: Wed, 6 Jan 2016 18:27:12 +0000 (UTC) User-Agent: KNode/4.14.2 X-User-ID: eJwNycEBwEAEBMCW4lhcOazov4RkvgN1cYY53LDYnBBhEbZ4S3zn73IKF8f0aCJjTnfPnZFHzBcge1IjbnxlDBXF Cancel-Lock: sha1:ESyJB6iD4+ut0kgEaJuYvVVv+c4= X-NNTP-Posting-Host: eJwVyMkRwDAIA8CWxCE5lGOc0H8JnuxzGTKdlaKSw5kzlR/SUQoynu6uhL3OvwMb+7himTkgXAn5D70= Xref: csiph.com comp.lang.javascript:29155 John Harris wrote: > On Tue, 05 Jan 2016 20:13:17 +0100, Thomas 'PointedEars' Lahn > wrote: >> John Harris wrote: >>> On Mon, 04 Jan 2016 15:27:13 +0100, Thomas 'PointedEars' Lahn >>> wrote: >>>> John Harris wrote: >>>>> On Sun, 03 Jan 2016 16:59:02 +0100, Thomas 'PointedEars' Lahn >>>>> wrote: >>>> Attribution *line*, _not_ attribution novel. >>> Agent won't let me make it one line. >> I strongly doubt that your software is that b0rked that it would not >> allow you to edit that part of the posting before you submit it, if all >> else fails. > > It appears that physical line lengths are built in to Agent. They > conform to the relevant standards. That is not the point, and having an attribution that is long but fits in one line is not the goal here. The point is that you are including information in the attribution that is superfluous; omitting that information would *easily* keep the attribution within one line. And how well you know that (this is not the first time we are discussing this). >>>>> The syntax says >>>>> identifier_b = identifier_a ; >>>>> The semantics are complicated. They say >>>>> If The storage area associated with identifier_a holds a >>>>> primitive (non-object) value >>>>> Then The storage area associated with identifier_b will now also >>>>> hold this primitive value, but a different instance of it >>>>> Else The object associated with identifier_a will now also be >>>>> associated with identifier_b >>>>> (Note : there are other ways of saying this) >>>> How did you get that idea? >>> By reading ECMA 262. >> If you think that ECMA-262 (which Edition?) is confirming your ideas, >> then you will have no difficulty citing the corresponding algorithms >> and referring explicitly to the relevant parts. > > This is true. > > Perhaps you are asking me to explain my conclusions. No, obviously I am requiring you to substantiate your claims so that I need not write them off as more examples of your misconceptions about ECMAScript like before. > I will do this, but it is best done in a separate article, It belongs in this thread, where your claims were made. A proper change of Subject header field value would be acceptable, though. > which won't be written today. No problem for me as long as it is written. Your other alternative is very simple: retract your claims. >> In any case, your newest attempt of trying to shift the burden of proof >> is unsuccessful. >> >> > > You asked me where I got it from. I told you. No, you did not. You made the new claim that the Specification substantiates your previous one, but you did not say how. Unless you at least cite explicitly the parts that you think substantiate the former (a quotation would be of advantage, too), that new claim is only based on your interpretation of what you read, and your interpretation can be wrong. As a result, so far your previous claim also lacks substantiation. Given that you have already claimed that ECMAScript would specify its conforming implementations to such a detail as memory access, which it obviously should not and does not, and that the implementation that is easier to program is one that does not implement your idea/follow your interpretation, your idea and interpretation are most likely wrong. -- PointedEars FAQ: | SVN: Twitter: @PointedEars2 | ES Matrix: Please do not cc me. / Bitte keine Kopien per E-Mail.