[Ironruby-core] Stupid to_clr_string

Sean Clark Hess seanhess at gmail.com
Fri Aug 15 12:38:50 EDT 2008


Ah, makes sense.  I'm totally unfamiliar with the way IronRuby is
implemented. Is it possible to switch it to a clr string any time it calls
any framework code? (like the invoke function I'm using).
~sean

On Fri, Aug 15, 2008 at 10:33 AM, Curt Hagenlocher <curth at microsoft.com>wrote:

>  This isn't a Silverlight issue but an IronRuby one.  A Ruby string simply
> isn't the same as a CLR string – the Ruby string is mutable while the CLR
> string is not.
>
>
>
> We need to come up with a cohesive plan for dealing with the difference
> before we can "fix" anything.
>
>
>
> *From:* ironruby-core-bounces at rubyforge.org [mailto:
> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Sean Clark Hess
> *Sent:* Friday, August 15, 2008 9:25 AM
> *To:* ironruby-core at rubyforge.org
> *Subject:* [Ironruby-core] Stupid to_clr_string
>
>
>
> Ok, I keep running into this over and over.  Whenever Silverlight passes a
> string to javascript, it comes out as some unreadable object.  You have to
> call to_clr_string to get it working.
>
>
>
> This is ok... You can monkey patch some of the javascript library code to
> fix it, but with HtmlPage.window.invoke, for example, it's not easy to do
> because it sends a variable number of arguments.
>
>
>
> Is this being fixed? Or is this something we're going to have to deal with
> for a while?
>
>
>
> Thanks
>
> ~sean
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20080815/42aeb56f/attachment.html>


More information about the Ironruby-core mailing list