Mercurial > pylearn
comparison doc/v2_planning/arch_src/plugin_JB_comments_YB.txt @ 1242:316410a38f6f
comment on Yoshua's comment on James architecture
author | Razvan Pascanu <r.pascanu@gmail.com> |
---|---|
date | Thu, 23 Sep 2010 12:10:14 -0400 |
parents | 067b2f9ba122 |
children | 808e38dce8d6 |
comparison
equal
deleted
inserted
replaced
1241:6801451a86bb | 1242:316410a38f6f |
---|---|
21 when possible, and just create another code for a new DBN variant when it can't fit?) | 21 when possible, and just create another code for a new DBN variant when it can't fit?) |
22 * am I missing something? | 22 * am I missing something? |
23 | 23 |
24 I am not convinced that any of the stated advantages can't be achieved in more traditional ways. | 24 I am not convinced that any of the stated advantages can't be achieved in more traditional ways. |
25 | 25 |
26 RP comment: James or anybody else correct me if I'm wrong. What I think James | |
27 proposed is just a way encapsulating different steps of the program in some | |
28 classes. These classes are serializable. They are not a programming language | |
29 per se. The way I see it is like dividing your program in a set of functions. | |
30 Each function is a control flow element applied to something ( like a CALL to | |
31 a python function ). The idea is to wrap this functions around something to | |
32 make them serializable, and also offer the added advantage that you have a | |
33 graph that presents the order in which you should call the functions and you | |
34 can play with that order. | |
26 | 35 |
36 That is why I was trying to convince James to re-write things ( using some | |
37 syntactic sugar) to make it look less intimidating ( I believe it can look | |
38 much more "traditional" that it looks right now). I think a programming | |
39 language might also be a overloaded term that so we might speak about | |
40 different things. But if all that his proposal does is to offer some wrapper | |
41 around python function that makes them serializable, and generate a execution | |
42 order graph in which you can possible do simple operations ( like | |
43 substitutions and replacements) I would not call it a programming language. | |
44 | |
45 I think the advantage of making the program aware where in its own execution | |
46 flow it is and what is its execution flow can be quite useful for automating | |
47 some of the things we want. |