M.-A. Lemburg wrote:
> May I suggest that you use a different name than "context" for
> this ?!
>
> The term "context" is way to broad for the application scopes
> that you have in mind here (like e.g. managing a resource
> in a multi-threaded application).
It's actually the broadness of the term 'context' which is appealing - the
examples in the draft documentation on SF are:
- resource management (synchronisation locks, generic 'closing')
- HTML tag matching
- Decimal arithmetic context
Any earlier version used 'suite managers' (partly to avoid confusing the hell
out of anyone ever exposed to Ruby's concept of blocks), but the 'context
management' term seems to more clearly describe what the protocol is for.
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.blogspot.com
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
