Re: Putting Carbon code into daemons

• Subject: Re: Putting Carbon code into daemons
• From: "stephen joseph butler" <email@hidden>
• Date: Thu, 11 Jan 2007 20:46:41 -0600
• Delivered-to: email@hidden
• Delivered-to: email@hidden
• Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=s1LiglZMm9Lfexf4eXYOXihhvEgQLoeVJ+OOTh1jPhYA1yDDchRL2X6wB1mZE7mo1mKR/h4nAD1BzkpENM6DLSbudwWd7BWZ1HY1dEMJUUG9QcCKUhKjT8a7iOe4TDx4GMPkT9NIyopHAV6ZT3Qr6Qp27v7SHKEJzAfJjmoGuto=

Are there any restrictions on putting Carbon code into OS X daemons?

I have a small existing Cocoa daemon written for 10.4. which is working
and now I want to move some code - namely some run loop code from a
Carbon app project into my Cocoa daemon project.

Is this a) safe to do and b) are there any gotcha's?

As long as you watch which frameworks you're linking to, I don't think
it is a problem. Here's a list of frameworks and whether they're safe
to use in daemons or not:

<http://developer.apple.com/technotes/tn2005/tn2083.html#SECFRAMEWORKCROSSREFERENCE>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

• Follow-Ups:
  • Re: Putting Carbon code into daemons
    • From: Mike <email@hidden>

• Prev by Date: Putting Carbon code into daemons
• Next by Date: Re: Putting Carbon code into daemons
• Previous by thread: Putting Carbon code into daemons
• Next by thread: Re: Putting Carbon code into daemons
• Index(es):
  • Date
  • Thread