A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-January/050977.html below:

[Python-Dev] Son of PEP 246, redux

[Python-Dev] Son of PEP 246, reduxPhillip J. Eby pje at telecommunity.com
Thu Jan 13 05:48:47 CET 2005
At 11:26 PM 1/12/05 -0500, Clark C. Evans wrote:
>Regardless,
>getting back to the main goal I had when writing PEP 246 -- your
>alternative proposal still doesn't seem to provide a mechanism for
>component developers to have a dialogue with one another to connect
>components without involving the application programmer.

Eh?  You still have adapt(); you still have adapters.  The only difference 
is that I've specified a way to not need "interfaces" - instead interfaces 
can be defined in terms of individual operations, and those operations can 
be initially defined by an abstract base, concrete class, or an "interface" 
object.  Oh, and you don't have to write adapter *classes* - you write 
adapting *methods* for individual operations.  This can be done by the 
original author of a class or by a third party -- just like with PEP 246.

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4