Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.mixmin.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Eric Bednarz Newsgroups: comp.lang.javascript Subject: Re: calling function within (function() {...})(); Date: Wed, 09 Nov 2011 20:13:33 +0100 Organization: Eric Conspiracy Secret Labs Lines: 16 Message-ID: References: <8928443.SEqChMirdb@PointedEars.de> <2015534.YEL58v44cs@PointedEars.de> Reply-To: ebednarz@gmx.net Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net UA3UXXk1u/403vkXMcGqYAwbnzS3wLg9QbZNrr99tU8MYedmul Cancel-Lock: sha1:MaazYwiPItuMQThcI9Ayd+E8Ems= sha1:tAjp6RVBroccUIQWTXkia6iaSU4= X-Eric-Conspiracy: There is no conspiracy User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (darwin) Xref: x330-a1.tempe.blueboxinc.net comp.lang.javascript:8177 Thomas 'PointedEars' Lahn writes: [function declarations vs. methods in ‘private’ scope] > Any potential safety gained this way only mitigates the unnecessary, > potentially harmful dependency introduced by Eric with the closure (by > contrast to the rather clean, original code). The whole purpose of the clean, original code was to introduce closures at some point. Well, either that, or there was a useless – albeit refreshingly clean – function expression. > It should be this.b(), > not x.b(). It must be exhausting, having all those opinions. :-)