> > 2009/9/17 Richard Gaskin <[email protected]> > > Given this, you should be able to simply refer to the long name of the > substack without needing to explicitly include its mainstack: >
Yes - the point is that the following give a result that is not only unexpected but plain wrong (go on - try it and see): > put the name of stack "revLibrary" into stackObject > put the long name of stack "revSaving" of stackObject = the long name of > stack "revLibrary" -- believe it or not this is true! > In my MVC libraries handlers frequently pass around the objects they acts on. So early on I put object references into a variable: put the long id of the target into targetObject and then pass the variable "targetObject" around. As such a handler that get passed a reference to a stack in a variable should be confident that it does what is expected. In my case it did not and added an object to the main stack and not the substack because of the above bug. As a passionate advocate for the language and its robustness - maybe a few a votes here <http://quality.runrev.com/qacenter/show_bug.cgi?id=8277> would get this annoyance fixed :) 2009/9/17 Robert Maniquant <[email protected]> > > COuld you precise which version 3.5 or 4 ? I recall having had some strange > behaviors related to stack name in variables, I think I took another route, > but that could explain it!! > Pretty sure it will be in all versions. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
