Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!sdrc!cinnet!kilian From: kilian@cinnet.com (Kilian Jacob) Newsgroups: comp.sys.amiga.programmer Subject: Re: Short Hello World Message-ID: <1991May29.040700.16292@cinnet.com> Date: 29 May 91 04:07:00 GMT Article-I.D.: cinnet.1991May29.040700.16292 References: <1991May22.221820.4348@nada.kth.se> Organization: Cincinnati Network, Cinti. OH Lines: 27 From article <1991May22.221820.4348@nada.kth.se>, by d88-skl@dront.nada.kth.se (Stellan Klebom): > In article <1991May22.132222.29285@cs.umu.se> dvljrt@cs.umu.se (Joakim Rosqvist) writes: >>Unfortunately, they are not as smart as you. They use: >> >>OldOpenLibrary: >> moveq.l #0,d0 >> jsr OpenLibrary(a6) >> rts >> >>6 bytes more than necessary! >> >> >>/$DR.HEX$ > > Fortunatly they are smarter than you! ;) If it was done in any other way, then > the SetFuction() ability would be lost... > The questions is whether you want OpenLibary changed via SetFunction() affect OldOpenLibrary(), too. I think the answer is no. To me it makes more sense to change OldOpenLibrary itself if you want it to change. -- /