Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!rutgers!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Short Hello World
Message-ID: <22003@cbmvax.commodore.com>
Date: 29 May 91 16:23:18 GMT
References: <1991May22.221820.4348@nada.kth.se> <1991May29.040700.16292@cinnet.com>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.
Lines: 21

In article <1991May29.040700.16292@cinnet.com> kilian@cinnet.com (Kilian Jacob) writes:
>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.

The answer is yes, OldOpenLibrary() needs to be affected by any SetFunction()
of OpenLibrary(), because it's supposed to be equivalent to
OpenLibrary(library,0L).  In every normal Amiga system, OpenLibrary()
is SetFunction()ed, because Exec doesn't know about loading disk-based
libraries.  A module called ramlib comes along after Dos is running
and takes care of that extra job by SetFunction()ing OpenLibrary()
and OpenDevice().

>-- /<ilian

     Peter
--
Peter Cherna, Operating Systems Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"If all you have is a hammer, everything looks like a nail."