Op 1 jul. 2012, om 19:38 heeft Jens Alfke het volgende geschreven: > It's always better to use an already-tested library than to roll your own, if > it's feasible.
Often you are not sure about the status of code you find online. Has it really been tested? Does it still work on my system, with my SDK? And worse of all, if something does break, how can I fix it if I don't understand what that code is actually doing? That is my greatest fear: not being able to support my own software because I made it rely on 3rd party code that I do not understand. But I get the idea, including more newly written code does of course mean more testing and more possible bugs. So if you find a trusted source for your wanted code, I guess it would be okay to use it, I would also do it. But just look at that stackoverflow.com link I gave earlier, and the discussions about the solutions given. It is not that easy to find quality code that you can build release quality products on, I think... I hope I am wrong, I need a few decoders and encoders and socket libraries myself currently ;-) [[[Brainchild alloc] initWithName:@"Richard Altenburg"] saysBestRegards]; _______________________________________________ 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
