Mercurial > pylearn

comparison doc/v2_planning/architecture.txt @ 1126:7ba1854f03e7

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 40c1461ce9ef
comparison
equal deleted inserted replaced
1125:5387666d49b4 1126:7ba1854f03e7
59 59
60 YB: I agree that lambdas are more flexible, but from the user's point of 60 YB: I agree that lambdas are more flexible, but from the user's point of
61 view it is really important to know what can swap with what, so that they 61 view it is really important to know what can swap with what, so that they
62 can easily plug-and-play. So even if informal, something in the spirit 62 can easily plug-and-play. So even if informal, something in the spirit
63 of an API must be described somewhere, and components should declare 63 of an API must be described somewhere, and components should declare
64 either formally or through comments what functionality 'type' they can take on. 64 either formally or through comments what functionality 'type'
65 they can take on.
65 66
66 Encapsulation vs. linearity 67 Encapsulation vs. linearity
67 --------------------------- 68 ---------------------------
68 69
69 A while ago, the Apstat crew went to fight "encapsulation" to propose instead 70 A while ago, the Apstat crew went to fight "encapsulation" to propose instead