[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

Subject: Re: What do we want in Carbon? (was Modern C++)
From: Eric Schlegel <email@hidden>
Date: Fri, 7 Nov 2003 14:00:03 -0800

On Nov 7, 2003, at 1:20 PM, Laurence Harris wrote:

Hey, perhaps in some of those cases you could introduce a time delay in the
code path that works around developer-induced problems. Then the code would
work, but there'd be a performance hit to motivate the developer to fix his
code. hehehe

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.

-eric
_______________________________________________
carbon-development mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/carbon-development
Do not post admin requests to the list. They will be ignored.

Follow-Ups:
- Re: What do we want in Carbon? (was Modern C++)
  - From: Chris Page <email@hidden>
- Re: What do we want in Carbon? (was Modern C++)
  - From: Laurence Harris <email@hidden>

References:
	>Re: What do we want in Carbon? (was Modern C++) (From: Laurence Harris <email@hidden>)

Prev by Date: Re: What do we want in Carbon? (was Modern C++)
Next by Date: xCode - Creating carbon exec w/o bundle
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

Home