FROM : Scott Anguish
DATE : Mon Feb 18 20:33:36 2008
I think this debate has passed the point of usefulness. It's probably
best to take it to private email.
If you feel the documentation is not explicit enough in this case,
file a bug.
Despite your assertion, there ARE binary compatibility requirements
within Apple. Bill is in an excellent position to know this since he's
an Apple engineer.
Scott
Apple Inc
Technical Publications, Cocoa and Developer Tools Group
On Feb 18, 2008, at 7:53 AM, Gregory Weston wrote:
>>
>> In light of the documentation, the binary compatibility
>> requirements, and the implementation for at least the past 6 years
>> -- if not the past 14 -- it would seem a rather pessimistic
>> conclusion.
>
> The documentation supports me more than you, the binary
> compatibility "requirements" don't exist, and the implementation
> aside from being irrelevant only supports your reading since
> October. Yes, it *is* a pessimistic stance, but that's the
> appropriate way to read such things. An API doc is a first cousin to
> a standards document; what isn't said is as important as what is
> and, in particular, if a behavior isn't promised as reliable then
> relying on it is an error.
DATE : Mon Feb 18 20:33:36 2008
I think this debate has passed the point of usefulness. It's probably
best to take it to private email.
If you feel the documentation is not explicit enough in this case,
file a bug.
Despite your assertion, there ARE binary compatibility requirements
within Apple. Bill is in an excellent position to know this since he's
an Apple engineer.
Scott
Apple Inc
Technical Publications, Cocoa and Developer Tools Group
On Feb 18, 2008, at 7:53 AM, Gregory Weston wrote:
>>
>> In light of the documentation, the binary compatibility
>> requirements, and the implementation for at least the past 6 years
>> -- if not the past 14 -- it would seem a rather pessimistic
>> conclusion.
>
> The documentation supports me more than you, the binary
> compatibility "requirements" don't exist, and the implementation
> aside from being irrelevant only supports your reading since
> October. Yes, it *is* a pessimistic stance, but that's the
> appropriate way to read such things. An API doc is a first cousin to
> a standards document; what isn't said is as important as what is
> and, in particular, if a behavior isn't promised as reliable then
> relying on it is an error.






Cocoa mail archive

