From c38198cfef84eb21cc61f689931a555444ec76fe Mon Sep 17 00:00:00 2001 From: Just van Rossum Date: Fri, 14 Jan 2005 19:01:09 +0000 Subject: [PATCH] fixed a couple of typos --- pep-0246.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pep-0246.txt b/pep-0246.txt index baa37b878..2e9cd0aa0 100644 --- a/pep-0246.txt +++ b/pep-0246.txt @@ -325,12 +325,12 @@ Guido's "Optional Static Typing: Stop the Flames" Blog Entry def f(X): X = adapt(X, Y) - # continue by using X according to protocol X + # continue by using X according to protocol Y In [4], the BDFL has proposed introducing the syntax: def f(X: Y): - # continue by using X according to protocol X + # continue by using X according to protocol Y to be a handy shortcut for exactly this typical use of adapt, and, as a basis for experimentation until the parser has been modified @@ -338,7 +338,7 @@ Guido's "Optional Static Typing: Stop the Flames" Blog Entry @arguments(Y) def f(X): - # continue by using X according to protocol X + # continue by using X according to protocol Y These BDFL ideas are fully compatible with this proposal, as are other of Guido's suggestions in the same blog. @@ -615,7 +615,7 @@ Questions and Answers appropriate adapter, but even then searching for the adapter and figuring out how to deploy the adapter takes time. - This technique enables supplierrs to work with each other + This technique enables suppliers to work with each other directly, by implementing __conform__ or __adapt__ as necessary. This frees the integrator from making their own adapters. In essence, this allows the components to have a