Forum: IronRuby using Ruby types in .NET: anything to watch out for?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Bb45e44f9e0c0b50551429d3feb214d1?d=identicon&s=25 Davy Brion (Guest)
on 2010-09-06 16:39
(Received via mailing list)
Hi all,

first of all: thanks for this great project and the effort you've put
into
it, it's very much appreciated :)

I plan on making extensive use of ruby object instances in my .NET code.
With that i mean that we have a certain object model written in Ruby,
and
we'd like to use that in our .NET code.  We're going to use those
instances
quite a lot, so i just wanted to check if there are any known pitfalls
to
watch out for when doing this.  The reason i'm asking is because most of
the
docs and the examples i've seen focus on the opposite approach: using
.NET
instances in Ruby.

I've done some preliminary experiments and my ruby instances work just
fine
when i call them from .NET... but i'm hoping to get some feedback here
from
people who have more extensive experience with this.

brs,
Davy
This topic is locked and can not be replied to.