Re: SIGIO and AppKit main loop
Re: SIGIO and AppKit main loop
- Subject: Re: SIGIO and AppKit main loop
- From: John Stiles <email@hidden>
- Date: Sun, 28 Mar 2004 16:03:54 -0800
CodeWarrior is fine if you can use the BSD libraries. (This is not the
default, oddly.)
If you have to use MSL, then yes, the POSIX layer demonstrates many
goofy and nonstandard behaviors. Tread lightly :)
On Mar 28, 2004, at 1:46 PM, Mike Davis wrote:
Speaking from personal experience, using async IO is bad news. It
works unless you have to be mixed in with CodeWarrior so beware.
I switched to mach messaging (MIG) to avoid my problems as I was
developing a framework with GCC but the client was using CW
8.something. Even worse, they were using CFM as a rule but had some
bits as mach with the crazy MSL versions of signalling, never mind the
regular POSIX APIs.
On 28 Mar 2004, at 22:16, email@hidden wrote:
To: Cocoa Development <email@hidden>
From: Michael Rothwell <email@hidden>
Subject: SIGIO and AppKit main loop
Date: Sun, 28 Mar 2004 11:57:29 -0500
I used SIGIO to implement an asynchronous SSDP listener with callback
notification, written in straight C.
Will I experience any problems using this bit of code in a Cocoa
application? In other words, will my use of SIGIO (and the associated
signal handler) clash with anything AppKit does?
Michael Rothwell
email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.