Why not use straight C functions? Sent from my iPad
> On Sep 13, 2014, at 20:45, Trygve Inda <cocoa...@xericdesign.com> wrote: > > I have a project that involves several different targets. > > Included in all this is a set of related utility methods that need to be > used by different sections of the code. I am wondering how is the best way > to do this so that I don't have the same utility methods written in > different places. > > 1. I could make a class MyUtilities that consisted of the 10 or so methods > as class methods and the class would have no instance methods or instance > variables. > > 2. I could make a singleton that put the methods as instance methods, but > also had no instance variables. > > Thoughts? > > I can't really make these methods a category on anything else. > > These methods are used to convert between an NSScreen, CGDirectDisplayID, > io_service_t, and a few other ways of dealing with screen identification. So > a category on NSScreen is not going to work since in some cases an NSScreen > is not known/used. > > Trygve > > > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/xcvista%40me.com > > This email sent to xcvi...@me.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
