• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: SIGIO and AppKit main loop
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SIGIO and AppKit main loop


  • Subject: Re: SIGIO and AppKit main loop
  • From: Michael Rothwell <email@hidden>
  • Date: Sun, 28 Mar 2004 20:45:57 -0500

So, long story short, if I don't intend to interact with
CodeWarrior-based code, I should be OK?

Would SIGPOLL be preferable?

Or is async I/O in general frowned upon with Cocoa? I'd be curious to
know of your 'personal experience' with async I/O on OSX.

Thanks,

-M

p.s. what is "MSL?"

Michael Rothwell
email@hidden

On Mar 28, 2004, at 7:03 PM, John Stiles wrote:

> 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.
_______________________________________________
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.


  • Follow-Ups:
    • Re: SIGIO and AppKit main loop
      • From: Michael Rothwell <email@hidden>
    • Re: SIGIO and AppKit main loop
      • From: Scott Thompson <email@hidden>
References: 
 >Re: SIGIO and AppKit main loop (From: Mike Davis <email@hidden>)
 >Re: SIGIO and AppKit main loop (From: John Stiles <email@hidden>)

  • Prev by Date: Suggestions on text display problem
  • Next by Date: NSTextView and memory usage
  • Previous by thread: Re: SIGIO and AppKit main loop
  • Next by thread: Re: SIGIO and AppKit main loop
  • Index(es):
    • Date
    • Thread