tag:blogger.com,1999:blog-22066395.post5343656316317885785..comments2023-05-08T03:59:05.247-04:00Comments on yokolet's notelets: RedBrdige's Sharing Variables, How It Worksyokolethttp://www.blogger.com/profile/12483973990218471737noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-22066395.post-27283920601330760952011-05-27T18:04:41.127-04:002011-05-27T18:04:41.127-04:00Local context models and variable behaviors won...Local context models and variable behaviors won't be against to the JSR223. JSR223 doesn't mention this sort of stuff at all. Ruby is a sophisticated language and is way beyond the JSR223 assumed to define API. For example, some other languages don't have idea of global/instance/local variables and their scopes.<br /><br />Besides, JRuby embedding API users use it in various yokolethttps://www.blogger.com/profile/12483973990218471737noreply@blogger.comtag:blogger.com,1999:blog-22066395.post-9449277251299497052011-05-16T15:55:52.743-04:002011-05-16T15:55:52.743-04:00I would go so far as to say that not only do JSR22...I would go so far as to say that not only do JSR223 developers not need this, this features goes against the JSR itself. When we specify a variable to have ENGINE_SCOPE, it should not be present in other engines that we create. However, that is the functionality that I am now seeing is that variables that are explictly set to have ENGINE_SCOPE are bleeding over to new engines, which was quite Joel McNaryhttps://www.blogger.com/profile/06225126875240186865noreply@blogger.comtag:blogger.com,1999:blog-22066395.post-9791413150263809902011-04-08T01:33:44.597-04:002011-04-08T01:33:44.597-04:00That's a lot to digest. Bookmarking this for l...That's a lot to digest. Bookmarking this for later because it is almost 1 o'clock in the morning.N. Nelsonhttps://www.blogger.com/profile/13557973750178909541noreply@blogger.com