Re: [Mac-emacs-devel] Overcoming 256MB Limitation?

[d p c. <dp...@qu...>]

Since i'm still reading up on carbon things you should correct my
misunderstandings here...

Andrew Choi <ak...@cs...> writes:

> d p chang <dp...@qu...> writes:
> 
>>> Once it is less buggy, what I want to do next is perhaps image
>>> support and better event handling.
>> 
>> I'm not sure what you mean by the later? (I've only used the unix
>> and normal macos versions where event handling seems fine). Is this
>> a carbon thing?
> 
> But there is an important area where the implementation can be
> improved.  Emacs basically uses X Windows's model of event handling.
> However, in the current Mac ports, input events are obtained by
> polling and passed through XTread_socket (mac_read_socket in 20.6).

However, the carbon model looks a lot like the x (windows too) model
so it should be more natural? I guess it would be more painful to
support classic and osx w/o ifdef-ing.

> Also I haven't figured out the relationship between (Unix) signals
> and event handling in a Carbon application.  So there is really no
> signal handling in the Mac OS X port.  E.g., it doesn't handle C-g
> at all.  It is quite important to get that to work, at least.

I don't see the connection between signals and events (other than
signalling from within an event callback).

\p
---
Luck is when preparation meets opportunity. --- Elmer Letterman