Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #29217
| From | Thomas 'PointedEars' Lahn <PointedEars@web.de> |
|---|---|
| Newsgroups | comp.lang.javascript |
| Subject | Re: Javascript Object Extensions Updated |
| Date | 2016-01-10 20:39 +0100 |
| Organization | PointedEars Software (PES) |
| Message-ID | <1862967.93ejQMdMOp@PointedEars.de> (permalink) |
| References | (8 earlier) <87r3hqxw37.fsf@bsb.me.uk> <XnsA58AED9E760CCeejj99@194.109.6.166> <87fuy6xlfz.fsf@bsb.me.uk> <2166962.mB4Gg9StQ4@PointedEars.de> <XnsA58BCC3B794F4eejj99@194.109.6.166> |
Evertjan. wrote: > Thomas 'PointedEars' Lahn <PointedEars@web.de> wrote on 10 Jan 2016 in > comp.lang.javascript: Again, it is called an attribution _line_, *not* an attribution novel. The e-mail address is irrelevant; the proper contact address is in the “Reply-To” header field in this case. The date is irrelevant; the statements made are relevant no matter when they were made, and if there is doubt, one can look into the “Date” header field of the precursor. If that is not available on the same news server, it is available in newsgroup archives. The newsgroup is already in the “Newsgroups” header field value of the precursor; and since there was no crosspost here, it is the same newsgroup as in your posting. So *all* of this is *superfluous* information in your postings. Why do you not simply omit it, and make your postings, and threads in which you participate, easier readable? And stop the address munging. When will you *ever* learn? >> lacks too many examples >> = a great number of examples that is too great is missing from it > > It might be a syntactically correct interpretation, That is a _semantic_ interpretation, and it is correct. “Syntactically correct” means something else. > and I do not think it is, Saying so does not make it so. > but even if it were, the sentence is utter nonsense. “Utter nonsense” in that it has no discernible meaning for you, or in that you do not agree with the statement? If the former, it means, if the “lacks way too many” is resolved, that, in the opinion of the author of the sentence, there are too few examples in the blog post (for a documentation). As a non-native speaker of English whose record shows that they are challenged with properly understanding even the simplest of English words and sentences, you should be slow to pass judgement as to the correctness of (my) interpretations, and the sense, of sentences in English – particularly when colloquial speech has been used. If the latter, then we are finally back on topic: Above said, the author of the sentence committed a fallacy in the first place by assuming that the referred blog post was intended to be a documentation. And *host* objects should not be augmented indeed. For good reasons that can be found in the newsgroup archive. After intense discussion, that has become consensus here since more than a decade (all of the people listed as “experts” in the blog post have been or still are regular contributors to this newsgroup). I would seem that the jQuery people, among others, had to learn it the hard way again; they are no longer augmenting host objects, but keep a registry for element augmentation. -- PointedEars FAQ: <http://PointedEars.de/faq> | SVN: <http://PointedEars.de/wsvn/> Twitter: @PointedEars2 | ES Matrix: <http://PointedEars.de/es-matrix> Please do not cc me. / Bitte keine Kopien per E-Mail.
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Javascript Object Extensions Updated Simon Blackwell <syblackwell@anywhichway.com> - 2016-01-07 14:29 -0800
Re: Javascript Object Extensions Updated "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-01-07 14:45 -0800
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-07 21:37 -0300
Re: Javascript Object Extensions Updated Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2016-01-07 17:43 -0800
Re: Javascript Object Extensions Updated "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-01-07 18:03 -0800
Re: Javascript Object Extensions Updated Simon Blackwell <syblackwell@anywhichway.com> - 2016-01-09 05:54 -0800
Re: Javascript Object Extensions Updated Simon Blackwell <syblackwell@anywhichway.com> - 2016-01-09 06:12 -0800
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-09 12:27 -0300
Re: Javascript Object Extensions Updated "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-01-09 17:22 +0100
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-09 13:31 -0300
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-09 13:31 -0300
Re: Javascript Object Extensions Updated "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-01-09 22:35 +0100
Re: Javascript Object Extensions Updated Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-01-09 21:49 +0000
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-09 19:06 -0300
Re: Javascript Object Extensions Updated "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-01-09 23:21 +0100
Re: Javascript Object Extensions Updated Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-01-10 01:38 +0000
Re: Javascript Object Extensions Updated "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-01-10 11:26 +0100
Re: Javascript Object Extensions Updated Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-10 13:32 +0100
Re: Javascript Object Extensions Updated "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2016-01-10 20:04 +0100
Re: Javascript Object Extensions Updated Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2016-01-10 20:39 +0100
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-10 17:09 -0300
Re: Javascript Object Extensions Updated Simon Blackwell <syblackwell@anywhichway.com> - 2016-01-09 14:01 -0800
Re: Javascript Object Extensions Updated "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2016-01-09 16:19 -0800
Re: Javascript Object Extensions Updated Aleksandro <aleksandro@gmx.com> - 2016-01-09 21:49 -0300
csiph-web