home *** CD-ROM | disk | FTP | other *** search
- Path: sn.no!not-for-mail
- From: tbk@sn.no (Thore Bjerklund Karlsen)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Demo/game to OS frien
- Date: 25 Jan 1996 19:14:14 +0100
- Organization: SN Internett
- Message-ID: <4e8h9m$mpc@sinsen.sn.no>
- NNTP-Posting-Host: sinsen.sn.no
-
- (Simon Brown)
-
- >> >>There is a big difference. If you know your code contains a bug,
- >> >>can FIX it. If it's someone elses code you have to work around
- >> >>making ugly hacks which Programmers like yourself don't like.
- >>
- >> >Let me call you an idiot.
- >>
- >> Let me call you an arrogant asshole. You deserve it.
-
- >Let me avoid any namecalling whatsoever.
-
- This was my first, and hopefully only time..
-
- >> >Have you ever seen a bug fix for a game ? a demo ? Oh, you do it all
- >> >right from the beginning ?
- >>
- >> Have you ever seen a bug fix called SetPatch? Oh, they did it a
- >> right from the beginning?
-
- >That's the point, isn't it? SetPatch is there, bugfixes for games aren'
-
- Oh, bugfixes for games aren't? Where have you been the last 100 years
- or so? :)
-
- >> I'm not saying that everybody has perfect coding skills or produc
- >> perfect bugfree code, I'm saying this: If you know that a syst
- >> routine contains a bug which makes your program fail in one way
- >> another - make your own routine if possible!
-
- >Indeed. But assuming that, *without definite knowledge*, and going your
- >own way anyway, is not the right thing to do.
-
- Without definite knowledge, no.
-
- >And if you know there's a
- >bug, you can make use of the routine in such a way as to avoid it, if t
- >is possible.
-
- If it is possible, yes. Perhaps I didn't make myself completely
- clear..
-
- __
- \\\__ Thore B. Karlsen % tbk@sn.no % C64-C128D-A1200-A2000C
- \XX/ Wowbagger/AFL&SSN % -c0d3r- % A1230/50MHz-2C4F/340MB
-
- Exo.4.20: And Moses took his mama and his sons, and set dem downon an ass
-
-