Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!hamilton
From: hamilton@uxc.cso.uiuc.edu
Newsgroups: comp.sys.amiga
Subject: Re: Help with SetFunction()
Message-ID: <172200092@uxc.cso.uiuc.edu>
Date: 16 Dec 87 00:13:00 GMT
References: <10004@stb.UUCP>
Lines: 32
Nf-ID: #R:stb.UUCP:10004:uxc.cso.uiuc.edu:172200092:000:1573
Nf-From: uxc.cso.uiuc.edu!hamilton    Dec 15 18:13:00 1987


michael@stb says:
> In article <22035@ucbvax.BERKELEY.EDU> bryce@hoser.berkeley.edu (Bryce Nesbitt) writes:
> >True, sort of.  Intuition itself does not loop back through the library
> >vectors.  Thus any program calling SizeWindow() would trigger, but
> >mousing arround would produce no results.
> 
> Its not just intuition. Dos library doesn't. None of the BCPL handlers do.
> Heck, Translator didn't.
> 
> Commodore, please, some of us are starting to do some very interesting stuff
> with this. WE NEED *ALL* system software to support the library vectors--
> INCLUDING DOS.LIBRARY. I was actually going to re-write dos.library in
> C and just throw out all BCPL support. ...
> Unfortunately, things like [handlers]
> etc. are still in BCPL, using the global vector, making it impossible.

    no, the global vector is BCPL's equivalent of the library vector.
dos.library and the handlers don't bypass it for internal calls; they
always go thru the GV.  thus, patch the GV, and you're in business.
i did this a long time ago to implement something like phil lindsay's
"monproc"; i stole the file-handler GV entries for things like pktwait().
your only real problem is identifying the GV entries and what they do.
    as for re-writing dos.library, you'll just have to rewrite the
handlers too.

	wayne hamilton
	U of Il and US Army Corps of Engineers CERL
UUCP:	{ihnp4,seismo,pur-ee,convex}!uiucuxc!hamilton
ARPA:	hamilton@uxc.cso.uiuc.edu	USMail:	Box 476, Urbana, IL 61801
CSNET:	hamilton%uxc@uiuc.csnet		Phone:	(217)333-8703
CIS:    [73047,544]			PLink:  w hamilton