• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Documentation frustrations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation frustrations


  • Subject: Re: Documentation frustrations
  • From: m <email@hidden>
  • Date: Sun, 10 Jul 2005 20:37:24 -0700

On Jul 10, 2005, at 7:59 PM, mmalcolm crawford wrote:

In many cases the documentation describes part of a potential solution space, but then doesn't put any bounds on it.

I've wondered about the "unbounded" and sometimes elliptical nature of some of the documentation (sorry, no concrete examples come to mind right now). I thought (perhaps foolishly) it was a strategy to avoid unnecessarily constraining future development of Cocoa (i.e. the less tightly documented the behavior is, the more freely it can be changed).


Is it fair to assume that this is not the case?

_murat

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Documentation frustrations (From: Erik Buck <email@hidden>)
 >Re: Documentation frustrations (From: Steve Weller <email@hidden>)
 >Re: Documentation frustrations (From: Uli Kusterer <email@hidden>)
 >Re: Documentation frustrations (From: mmalcolm crawford <email@hidden>)

  • Prev by Date: Re: Why does this leak memory?
  • Next by Date: Re: Why does this leak memory?
  • Previous by thread: Re: Documentation frustrations
  • Next by thread: Re: Documentation frustrations
  • Index(es):
    • Date
    • Thread