Re: What do we want in Carbon? (was Modern C++)

• Subject: Re: What do we want in Carbon? (was Modern C++)
• From: David McLeod <email@hidden>
• Date: Mon, 10 Nov 2003 14:57:25 -0800

On Nov 7, 2003, at 14:00, Eric Schlegel wrote:

Actually, we do something very like that. When we introduce workarounds for a specific application, we (almost) always tie the workaround to a specific version or versions of the application - usually, the currently shipping version. So if FileBuddy version 22.4 happened to be incompatible with Mac OS 10.9, we would add a workaround that only applies to version 22.4; when you ship version 22.5, the workaround will cease to apply. We also always notify the developer of the problem that we find. That way, the developer has both the knowledge of what is needed to fix the bug, and an incentive to fix it in the next version of the application.

Unfortunately, this actually bit us relatively recently. We found that the in-development version of Palm Desktop exhibited a bug where the release version did not. It took us a while to figure out that it was something Apple had worked around[*].

Now, granted, I went through my archives and there was a discussion with an Apple engineer who said he'd put in a workaround for this bug, but it wasn't made clear to us that it would only apply to that specific version of our application, so we didn't realize we'd need to fix it before releasing another version.

[*] And rightly so: The offending code (which dates back to System 6 days) depended on a reverse-engineered system data structure. Even more unfortunately for us (read "me"), its use of this data was difficult to figure out and it took a while to come up with a clean alternative implementation for it.

• Prev by Date: Re: StandardAlert without default button?
• Next by Date: Re: Metal Buttons in Carbon apps
• Previous by thread: Re: What do we want in Carbon? (was Modern C++)
• Next by thread: Re: What do we want in Carbon? (was Modern C++)
• Index(es):
  • Date
  • Thread