Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!feeder.erje.net!news.internetdienste.de!news.tu-darmstadt.de!news.belwue.de!newsfeed.ision.net!newsfeed2.easynews.net!ision!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Content-Type: text/plain; charset="UTF-8" Message-ID: <4781699.ypaU67uLZW@PointedEars.de> From: Thomas 'PointedEars' Lahn Reply-To: Thomas 'PointedEars' Lahn Organization: PointedEars Software (PES) Date: Sun, 13 Nov 2011 00:42:52 +0100 User-Agent: KNode/4.4.11 Content-Transfer-Encoding: 8Bit Subject: Re: David Mark's Javascript Tip Du Jour - Volume #1 - Tip #1234 - How to Measure Element Dimensions Newsgroups: comp.lang.javascript References: Followup-To: comp.lang.javascript MIME-Version: 1.0 Lines: 38 NNTP-Posting-Date: 13 Nov 2011 00:42:54 CET NNTP-Posting-Host: 08b440b7.newsspool3.arcor-online.net X-Trace: DXC=hfcm3:\9idSYI9]OHn9o5^McF=Q^Z^V3X4Fo<]lROoRQ8kF]g3QkX_`T\dc@eFOeo^Z X-Complaints-To: usenet-abuse@arcor.de Xref: x330-a1.tempe.blueboxinc.net comp.lang.javascript:8272 Eric Bednarz wrote: > "Richard Cornford" writes: >> document.write( >> "" >> ); >> >> The cargo-cult programming structure is the first (left-most) string >> concatenation operation. The final (right-most) string concatenation >> operation has some justification in some contexts. Its use in those >> contexts demonstrates a shallow understanding of the reasons for its >> use (as there are more efficient, shorter and more formally correct >> alternatives), and it was almost certainly that shallow understanding >> that inspired the real cargo-cult structure to the left. However, One >> context where the final (right-most) concatenation is purposeless is >> when it is found in an imported JS file, which is of course where >> Google's code search is finding it. So that too is pushing cargo-cult >> programming in the contexts where it is being found above. > > I’m getting the impression that you think that the purpose of splitting > and concatenating the generic identifier is somehow related to escaping > the ETAGO delimiter (‘ to Norton ‘Internet Security’ inserting it’s dreaded SymError function > after the first instance of anything that looks like the start tag of a > script element (and ususally messing things up in the process). Suppose that was the case, then it would be a Bad Idea to work around that. Either it is a bug in Norton InSecurity, then working around it will help to keep it forever, having everyone to jump forever through the hoops that Symantec's incompetent, greedy developers once set up. Or it is a feature, then one would ignore the user's wishes, which is always a bad idea. PointedEars -- Danny Goodman's books are out of date and teach practices that are positively harmful for cross-browser scripting. -- Richard Cornford, cljs, (2004)