On Thu, Jun 12, 2008 at 8:40 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > Ideally, I would like for those considerations [i.e. whether an access is > expensive] > to not enter into the API > design. I'd rather keep it clean, with sufficient documentation to give > hints about any additional costs involved. Logically .alive is a property, > so I'd like to write it that way.
I beg to differ. Ideally, API design should suggest which operations are efficient and which ones aren't, in order to (subconsciously) help the developer develop a mental model about the performance characteristics of an API. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
