Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.datemas.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Content-Type: text/plain; charset="ISO-8859-1"
Message-ID: <7182976.Ku1byVuyr4@PointedEars.de>
From: Thomas 'PointedEars' Lahn <PointedEars@web.de>
Reply-To: Thomas 'PointedEars' Lahn <usenet@PointedEars.de>
Organization: PointedEars Software (PES)
Date: Thu, 29 Aug 2013 15:16:19 +0200
User-Agent: KNode/4.10.5
Content-Transfer-Encoding: 7Bit
X-Face: %i>XG-yXR'\"2P/C_aO%~;2o~?g0pPKmbOw^=NT`tprDEf++D.m7"}HW6.#=U:?2GGctkL,f89@H46O$ASoW&?s}.k+&.<b';Md8`dH6iqhT)6C^.Px|[=M@7=Ik[_w<%n1Up"LPQNu2m8|L!/3iby{-]A+#YE}Kl{Cw$\U!kD%K}\2jz"QQP6Uqr],./"?;=4v
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXTxa4RFk5dUWANED8PFEfy7+MGBiW+n3ZNF/QuAAACaElEQVQ4jVXUwVOcMBQG8Dc7Rc4PUntdWV2uxjDpGaGeozOp1woar4jd5t/v9wLstMwsA/ntlxdCAgUc1hjTc9/JCZfGoo3wG3HdmdAWrIJRHe7GM/TmpY5VFefuVcAkkPbLIaN8rmPmjloyZxgyR3GuJ4K0AGtJ2htz8o7yqikm759fldQXaMpbDzjKAG+8v+AugVTOPO5DOjLvGtUYQwh0CPjnVMyGd+8/GfUB5nLKJDD2aLDh5HYyMDJGDwQIo2ZmZcKbowNmAdB/AzyFhrmF2MHRb0QJJfaAnwGB6orZhoykLzJtGwF/xpYxI1dswomiUj3gTuAIqCn/4C7cULwGNBtwMTk3Y4LfKB5YUaOKBKYtpplm7u0vip8tU1NWWyI/7XdcSuIDoMt6rVHMWT0DbjHPGqDqZVSa6zleLcUTcIKLoMv3ueJluALtAo9B302zPPlrtiVScRdCjXvVh3e3JpYa/jjkuC9N+LrBMlz/eAN4eQijX2EdLo6c5tGGHwLyHFtXk89dDGHwCVhG9T0S/j55AhRZgkMCmUQXJ49TnS1wnQDvw0eAh9ICeMmEFbCnPMFzjAvsWoEWEFdYEx+S0MoUZ1gT1wId8+AF3Bl2OoEu906AUHx5VLw/gXYg/x84loOah/2UYNrgiwSwGO7RfUzVBbx/kgpckumGOi6QirtD6gkLTitbnxNol47S2jVc2vsN5kPqaAHT8uUdAJM4v/DanjYOwmUjWznGfwB7sGtAtor5BgofDuzaRj4kSQAqDakTsKORa3Q3xKi3gE1fhl71KRMqrdZ2AWNNg/YOhQyrVBnb+i+nEg4bsDA+egAAAABJRU5ErkJggg==
Subject: Re: Multiple image preload construct?
Newsgroups: comp.lang.javascript
References: <kvidas$lib$1@news.albasani.net> <kvire7$ca3$1@speranza.aioe.org> <2725916.yAnYnyUf7L@PointedEars.de> <kvj576$9oj$2@dont-email.me> <2920459.yuR5o6d9W1@PointedEars.de> <kvm9oa$nja$1@dont-email.me>
MIME-Version: 1.0
Lines: 50
NNTP-Posting-Date: 29 Aug 2013 15:16:20 CEST
NNTP-Posting-Host: ccb5e70e.newsspool1.arcor-online.net
X-Trace: DXC=5`VDHB6^8K;T2Rfi6<W9f5ic==]BZ:af>4Fo<]lROoR1nkgeX?EC@@0E^]7Dg`Z:Q:DZm8W4\YJN<b@mF9jNikd5mA0dJ;NON0?L<L`kOU`_j>
X-Complaints-To: usenet-abuse@arcor.de
Xref: csiph.com comp.lang.javascript:21096

Cezary Tomczyk wrote:

> On 2013-08-28 01:27, Thomas 'PointedEars' Lahn wrote:
>> Cezary Tomczyk wrote:
>>> On 2013-08-27 23:02, Thomas 'PointedEars' Lahn wrote:
>>>> Ken wrote:
>>> [...]
>>>>> Now you can call the function:
>>>>>
>>>>>        loadImages(myArray, loadDone);
>>>>>
>>>>>        function loadDone(result)  {
>>>>>            console.log('All images loaded!');
>>>>>            /// result contains an array with the Image elements
>>>>>        }
>>>>
>>>> Function expressions are widely supported by now, especially where
>>>> console.log() is supported [1]:
>>>>
>>>>     loadImages(myArray, function (result) {
>>>>       console.log('All images loaded!');
>>>>       /* result contains an array with the Image elements */
>>>>     });
>>>
>>> [...]
>>>
>>> While function expressions support is fine now then passing as a
>>> parameter in the "loadImages" function with long code can make whole
>>> "loadImages" later harder to maintenance.
>>
>> (_maintain_)  True.  OTOH, functions/methods should not be long.
> 
> Exactly what I meant.

I do not think so.  You have argued that using function expressions in 
function calls can pose a readability issue because functions can be long.  
I have argued that functions/methods should not be long in the first place 
(but larger pieces should be moved into separate functions/methods, which 
are then called in the original function/method).  So the problem you see is 
not supposed to exist in well-written code in the first place.

> Regarding "_maintain_" - thanks.

You're welcome.
 
-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.