Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Death of jGNEFilter?
Message-ID: <9068@hoptoad.uucp>
Date: 23 Nov 89 20:49:55 GMT
References: <2323@hudson.acc.virginia.edu>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 27

In article <2323@hudson.acc.virginia.edu> cak3g@astsun8.astro.Virginia.EDU
(Colin Klipsch) writes:
>I just read a recent article in this group which suggested that
>the days of jGNEfilter may be numbered.  (This is a low memory
>global which contains a pointer to an event filter routine.)

The days of all low-memory globals are supposedly numbered, presumably
to reduce context switching overhead in future releases of the
operating system.

>If I wish to remain compatible with future Macs (as I do in fact), how
>does one respond to events without using jGNEFilter?  Will there be some
>new method?  Is there a more subtle way of responding to events of
>which I am not aware?

Sure, just tail patch GetNextEvent!  Seriously, the answer to your
question is that there is no way to do this kind of thing and be
compatible with the guidelines.  You can either tail patch, which may
break now or soon, or use jGNEfilter, which may break in 1991.  I'd go
for the latter, that is, keep doing what you're doing now.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"But don't you see, the color of wine in a crystal glass can be spiritual.
 The look in a face, the music of a violin.  A Paris theater can be infused
 with the spiritual for all its solidity."
    -- Lestat, THE VAMPIRE LESTAT, Anne Rice