# HG changeset patch
# User Yoshua Bengio <bengioy@iro.umontreal.ca>
# Date 1284562105 14400
# Node ID 5387666d49b47c2b08ae02d24ffae7f939feabde
# Parent  0f184b5e7a3f58508e1521fe864f177e6c8a91a5
YB: comment on lambdas vs API for architecture.txt

diff -r 0f184b5e7a3f -r 5387666d49b4 doc/v2_planning/architecture.txt
--- a/doc/v2_planning/architecture.txt	Wed Sep 15 10:25:35 2010 -0400
+++ b/doc/v2_planning/architecture.txt	Wed Sep 15 10:48:25 2010 -0400
@@ -57,6 +57,12 @@
 just not essential to choose an API that will guarantee a match, or indeed to
 choose any explicit API at all.
 
+YB: I agree that lambdas are more flexible, but from the user's point of
+view it is really important to know what can swap with what, so that they
+can easily plug-and-play. So even if informal, something in the spirit
+of an API must be described somewhere, and components should declare
+either formally or through comments what functionality 'type' they can take on.
+
 Encapsulation vs. linearity
 ---------------------------