I quite commonly fix bugs by refactoring all the lengthy routines into several shorter ones.
I'll do that especially when I can't determine the cause of a bug; instead I'll just look around for messy source then tidy it up. That has a way of making bugs go away. On 6/1/15, Charles Srstka <cocoa...@charlessoft.com> wrote: > On Jun 1, 2015, at 6:39 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: >> >> On Jun 1, 2015, at 15:14 , Charles Srstka <cocoa...@charlessoft.com >> <mailto:cocoa...@charlessoft.com>> wrote: >>> >>> Which is not at all, actually: >> >> The answer is "not at all" only with the modern ABI. 32-bit Mac >> compilations will conflict. > > That's true. Also, code written for the Mac Plus using THINK C 3.0 will > conflict. However, compilation targets that people are actually still using > in 2015 will not conflict. > > Charles > > _______________________________________________ > > 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/mdcrawford%40gmail.com > > This email sent to mdcrawf...@gmail.com -- Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. _______________________________________________ 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
