From mint-bounce@lists.fishpool.fi Sun Dec 6 20:27:31 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Ol9XAGDBHNoxpCXUf/Fqs5MqIQGNi0fUQwiaHcXhabg=; b=rgsZEkN2whbjrrbCegVeoe3O75ZHzfy3kwAGODSjN95/KeiyAK3xWGA+PiGxt3TRDT cEKoyKmlr5H+AqsQDibPr65P8TiUE7D9sO3FVS6Nhxs6KUskx8W5umfqwmnvQlVP9/2N tQgOStfEXH3CYNub+w6nx5D7XzqWl5bZK20O8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Ix3jf30CwcMf8rj10HdtMrf/ueDZrVlUxYpmgo0MvYbe242iLnNalrRNTxEy0S37km WJ79kkcZru78pWVrSzWI0xz+pX8f77juA8jfbn/l1tmK7cpHn1+7wmhslzj1wHIRvtNJ 4UD0k9YwYgr2Fg/mCEYRybZ66OU0KA3d8cvKY= MIME-Version: 1.0 In-Reply-To: <4B1C3B79.9050704@chello.nl> References: <11a6f2b10912031803h290d38a8i916fc270ce6c6d76@mail.gmail.com> <11a6f2b10912050321p7918ef60gb17ba429f719b4e9@mail.gmail.com> <752526d20912050438o49cf5e4fw37e1d423afcd2935@mail.gmail.com> <11a6f2b10912050915r6e8d3e5ejfec9970990326f25@mail.gmail.com> <4B1AF6D9.5030704@freesbee.fr> <11a6f2b10912060757j55cdc533re2d452f7cb8b780f@mail.gmail.com> <11a6f2b10912060759i75e3f72sf7bf3bc78a6399df@mail.gmail.com> <4B1C3B79.9050704@chello.nl> Date: Mon, 7 Dec 2009 12:24:52 +1100 Message-ID: <11a6f2b10912061724w433ef061n5fb094e46a2e771f@mail.gmail.com> Subject: Re: [MiNT] XaAES crash errors From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Mon, Dec 7, 2009 at 10:17 AM, Henk Robbers wrote: > Paul Wratt wrote: >> >> First, thank you ALL for your replys > >> ALSO, the question that was related to *, **, an &, my current >> solution is to NOT use intermediate functions. This just meeans "code >> double ups" for certain functions which was my greater concern (other >> people reading the code, and extra binary space taken), but I can look >> at that later on, when I do "have more experience". It is possible >> that what I have will work, but I was concerned that it may have >> contributed to the "inital crash". > > I forgot to mention another cause of grand software disasters. > Code duplication. Or what I would call "copy paste programming" > Even if you have the intention to remove the duplication later > on, it is already too late. The duplication is already there. > First you have to remember every duplicate you have ever made. > Which is almost impossible. > Second some duplcates may have diverged in the mean time and > cannot be removed anymore. Your progam seems to work, so you leave > it in the end. Your successors aren't aware of these things > and wonder why the program behaves unpredictable in what seem > to be similar circumstances. > > -- code duplication: functions that contain code the majority of which is duplicated. copy paste programming: name a programmer who hasn't ...