Mercurial > pylearn
changeset 1126:7ba1854f03e7
YB: comment on lambdas vs API for architecture.txt
author | Yoshua Bengio <bengioy@iro.umontreal.ca> |
---|---|
date | Wed, 15 Sep 2010 10:49:48 -0400 |
parents | 5387666d49b4 |
children | 7207f86a661f |
files | doc/v2_planning/architecture.txt |
diffstat | 1 files changed, 2 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- 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 ---------------------------