Forum: IronRuby Standard Libraries Support

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Shay F. (Guest)
on 2009-05-29 23:21

I'm trying out the different standard libraries via IronRuby and some
throw errors once I try to require or use them.
The problematic ones are:

Also resolv and resolv-replace do not work but I guess it's because of
their win32 requests.

Should the above libraries work or is it a bug?

Jim D. (Guest)
on 2009-05-30 00:15
(Received via mailing list)
OpenSSL is being worked on by Jirapong. The other ones probably need to
be rewritten in C#.

Feel free to file bugs, or claim a library to work on ;)


...there is no try
Shay F. (Guest)
on 2009-05-30 01:10
So just to make sure - there are no plans of making those work for V1.0,

Thanks Jim!
Jim D. (Guest)
on 2009-05-30 02:13
(Received via mailing list)
Here's a quick rundown (~30mins worth of looking at these libraries)

RSS should work, it appears there is a bug in there with Class.inherited
Tracking with CodePlex 1483

We need to figure out what the ObjectSpace finalizers really do, and if
we can implement those methods.
Tracking with CodePlex 1484

Uses fork, so it will not work unless we completely re-implement it. The
workaround would be having someone port the win32-open3 gem to C#
Tracking with CodePlex 1485

Jirapong is working on this.

Uses Thread.exclusive, which is defined in the thread standard library
(as opposed to the Thread builtin class), which needs to be ported.
Tracking with CodePlex 1485

Uses ObjectSpace#id2ref and it may be reliant on the CRuby GC internals
Tracking with CodePlex 1487

Resolv and resolv-replace should be made to work, but they require us to
figure out what portions of win32 they need.
Tracking with CodePlex 1488

Ideally all of these should work for 1.0, but we may not have resources
to do them. Anyone who wants to is welcome to help bang at them to
narrow down the bugs, and port the needed libraries.

...there is no try
Jimmy S. (Guest)
on 2009-05-30 23:50
(Received via mailing list)
If you know an existing Ruby application which depends on these
libraries, then that'll make it more worthwile to get them working.


On May 29, 2009, at 2:13 PM, "Shay F." <removed_email_address@domain.invalid>
This topic is locked and can not be replied to.