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

diff -r 5387666d49b4 -r 7ba1854f03e7 doc/v2_planning/architecture.txt
--- a/doc/v2_planning/architecture.txt	Wed Sep 15 10:48:25 2010 -0400
+++ b/doc/v2_planning/architecture.txt	Wed Sep 15 10:49:48 2010 -0400
@@ -61,7 +61,8 @@
 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.
+either formally or through comments what functionality 'type' 
+they can take on.
 
 Encapsulation vs. linearity
 ---------------------------