Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.42!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!217.188.199.168.MISMATCH!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Content-Type: text/plain; charset="UTF-8"
Message-ID: <1550675.qVoOGUtdWV@PointedEars.de>
From: Thomas 'PointedEars' Lahn <PointedEars@web.de>
Reply-To: Thomas 'PointedEars' Lahn <cljs@PointedEars.de>
Organization: PointedEars Software (PES)
Date: Thu, 17 Nov 2011 23:54:08 +0100
User-Agent: KNode/4.4.11
Content-Transfer-Encoding: 8Bit
Subject: Re: Difference between findPos("divThis") and findPos(divThis)
Newsgroups: comp.lang.javascript
References: <j9olie$dsd$1@dont-email.me> <4775241.ypaU67uLZW@PointedEars.de> <j9p403$e80$1@dont-email.me> <2394720.ArG6xLiZAS@PointedEars.de> <j9p7t8$98q$1@dont-email.me> <j9pas5$ah2$1@speranza.aioe.org> <j9pb43$ah2$2@speranza.aioe.org> <j9pf87$rka$1@dont-email.me> <j9phhk$s3i$1@speranza.aioe.org> <4ec07ef1$0$28711$a8266bb1@newsreader.readnews.com> <j9q83e$b9m$1@speranza.aioe.org> <4ec11fb1$0$28605$a8266bb1@newsreader.readnews.com> <j9repq$vth$1@speranza.aioe.org> <4ec15e82$0$28617$a8266bb1@newsreader.readnews.com> <c303c6d2-b4c9-4057-8040-d908367c81f3@p2g2000vbj.googlegroups.com> <p6OdndndsIabIlzTnZ2dnUVZ8rKdnZ2d@giganews.com> <af7d752e-e9ef-491e-9729-365186b7a148@r9g2000vbw.googlegroups.com> <9iles3FnvhU1@mid.individual.net>
Followup-To: comp.lang.javascript
MIME-Version: 1.0
Lines: 48
NNTP-Posting-Date: 17 Nov 2011 23:54:08 CET
NNTP-Posting-Host: a8c9ab68.newsspool3.arcor-online.net
X-Trace: DXC=QU;CCV_6dA=]E=H1Q9`787McF=Q^Z^V384Fo<]lROoR18kF<OcfhCO;jWdeJAGglJ1DZm8W4\YJN<;?f@h5gMfb<ObTfU2klSE>eCcZnA96a>1
X-Complaints-To: usenet-abuse@arcor.de
Xref: x330-a1.tempe.blueboxinc.net comp.lang.javascript:8397

Frobernik wrote:

> You could squeeze more out of the available space and avoid the use of a
> var completely
> 
> Using the original example
> 
> function findPos(obj) {
>      var w = obj.offsetWidth;
>      var h = obj.offsetHeight;
> }
> findPos(divThis)
> 
> becomes :-
> 
> function findPos(obj, w, h) {
>      w = obj.offsetWidth;
>      h = obj.offsetHeight;
> }
> findPos(divThis)
> 
> another style/variant could be
> 
> function findPos(obj, name, colour, b, c) {
>      name = obj.name;
>      colour = obj.colour;
>      b = 17;
>      c = [{s:'monkey', x:'male', a:3}, {s:'elephant',x:'female',a:7}];
> }
> findPos({name:'df', colour:'green'})

(Jorge, is it you?)

We have been over this.

Declaring arguments instead of local variables may be great for code golfing 
(140 characters maximum), but it is a Really Bad Idea for all other code.  
To begin with, by looking at the code you cannot tell whether you are 
modifying an argument or not.  Editors and linters which can differentiate 
between arguments and local variables could not tell as well.


PointedEars
-- 
> If you get a bunch of authors […] that state the same "best practices"
> in any programming language, then you can bet who is wrong or right...
Not with javascript. Nonsense propagates like wildfire in this field.
  -- Richard Cornford, comp.lang.javascript, 2011-11-14