I find out this solution too. I think returning value is not an important thing! What is the current mechanism of eval() right now?
On Nov 14, 6:56 am, kangax <[EMAIL PROTECTED]> wrote: > On Nov 13, 10:30 pm, RobG <[EMAIL PROTECTED]> wrote: > > > On Nov 14, 7:39 am, Ehsun <[EMAIL PROTECTED]> wrote: > [...] > > There are work arounds, but best to avoid eval'ing scripts altogether. > > Yeah, there's a `globalEval` function scheduled for near future > releases. When running in environment that doesn't support `eval`ing > in a global scope, `globalEval` would fall back to a script element > insertion. That's one of the ways to avoid `eval` (although making it > hard to get evaluated expression's return value) > > > > > -- > > Rob > > -- > kangax --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~----------~----~----~----~------~----~------~--~---
