On Tue, Jul 26, 2011 at 02:19:25AM -0700, Nando Sola wrote: > > I've just arrived to the office after a short vacation. I'll test your > code immediately.
Hello Nando, I hope you could relax and enjoy the free time. Sorry for the late reply. > As for "rethinking forget & lose", It'll certainly spare a few lines > of code to our process definitions (and perhaps ruote community's) and > will help clear some concepts. Please let us know the way we could > assist you here, in case you decide to take on this modifications. It gravitates around the table at http://ruote.rubyforge.org/common_attributes.html#lose Since a forgotten branch/expression may survive its parent expression, the assumption is that once it is forgotten, the variables of the parent are not accessible to it anymore (tough the parent's variables get copied). In other words, we don't trust the parent will be here anymore. https://github.com/jmettraux/ruote/blob/02846f556853823590393807050de51f8300997e/lib/ruote/exp/flow_expression.rb#L778-799 We could start to say, as long as the parent is alive, it's OK to look up variables throught it, when it's dead, oh well, variables simply disappear. So we have to think about the big picture before making any change to that current behaviour. Open to suggestions. Cheers, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
