Mercurial > pylearn
comparison doc/v2_planning/arch_src/plugin_JB_comments_RP.txt @ 1218:5d1b5906151c
I did not fully get the argument against what I wrote ..
author | Razvan Pascanu <r.pascanu@gmail.com> |
---|---|
date | Wed, 22 Sep 2010 13:00:39 -0400 |
parents | 5a8930e089ed |
children | 35fb6e9713d2 |
comparison
equal
deleted
inserted
replaced
1217:c0515c0dfef9 | 1218:5d1b5906151c |
---|---|
85 mix Theano graph building with this control-flow business. | 85 mix Theano graph building with this control-flow business. |
86 | 86 |
87 Consequently, I think I will remove the BUFFER_REPEAT construct since that is | 87 Consequently, I think I will remove the BUFFER_REPEAT construct since that is |
88 really an expression masquerading as a control flow statement, and I will | 88 really an expression masquerading as a control flow statement, and I will |
89 remove FILT too. | 89 remove FILT too. |
90 | 90 |
91 RP asks: | |
92 | |
93 I understand now the difference between what you wrote and what I had in | |
94 mind. Though I don't undestand the argument against it. Do you mean to say | |
95 that writing it the way I proposed implies a much more complicated backbone | |
96 framework which will take us to long to develop? Or is there something else | |
97 that you meant ? | |
98 | |
99 |