Talk:IronRuby

comment

It is a little bit unclear whether IronRuby is a compiler that generates .NET code (Ruby->.NET) or just a Ruby interpreter which runs on the .NET platform and not directly on hardware.

IronRuby is a compiler, which operates in two modes. One is directly compiling directly to .net assemblies containing .net IL like C# and VB.NET compilers do. The .net assemblies are then just-in-time compiled (jitted) to machine code at the moment of execution. The other mode is immediate or interactive mode (which gives the illusion that it is being interpreted, but is actually being compiled). As soon as an expression is entered, it is compiled to a dynamic method containing IL which is jitted to machine code. The only difference between the two methods is that the on-disk assemblies are not created in interactive mode. The code translations (source -> IL and then IL -> native code) happen exactly once, which is the basic definition of a compiler. Same goes for IronPython and PowerShell, the running code is actually compiled, not interpreted. --soum ^talk 18:24, 26 July 2007 (UTC)

Cross-Platform

I have one question, which doesn't seem to be clear in the article. It says IronRuby is cross platform? Does this mean it runs/compiles on Windows, Mac OS X & Linux? Does the code have an IDE associated with it (such as Visual Studio Express, or is it just Visual Studio Standard & above), or does one have to edit the code directly from a text editor? I suppose if the IDE associated with it is Visual Studio then the IDE is not cross platform? --Nathaniel (talk) 07:45, 1 April 2009 (UTC)

see the Mono support. It may compile and run on all platforms supported by Mono, but as the IronRuby team only test it on Windows / MS .NET (and mainly rely on the community to test it on Mono), it depends. Sometimes it works, sometimes not (theres a specific repository for specific Mono patches (see here). As for the IDE, I assume that any IDE that edit Ruby code will work, except for IronRuby / .NET / Mono interoperability specific stuff. Hervegirod (talk) 21:07, 1 April 2009 (UTC)

Mono support

User:Ronark removed the Mono support paragraph because it seemed it relied on blogs only. However, half of the sources were not blogs, but came from the official developer thread for the project. I put back this section, but removed all blogs references. It seems important (in an Encyclopedia POV) to know that this project is only tested (for the moment) on Microsoft .NET (which is I think the main reason why it's not always working on Mono). Hervegirod (talk) 13:27, 1 February 2009 (UTC)

Death

What is the official definition of "dead"? This article (currently) says that IronRuby is dead. Typically dead means that the person or thing is incapable of nothing anything more. Is IronRuby incapable of nothing anything more? Or is it still useful? Is it just not being improved because there is nothing more to be done or are there bugs that need to be fixed that are not being fixed? Is it possible or impossible for the project to continue? The word "dead" in this context is highly imprecise and subjective. Sam Tomato (talk) 18:14, 19 October 2014 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 9 external links on IronRuby. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20070612185141/http://www.iunknown.com/2007/05/microsoft_and_i.html to http://www.iunknown.com/2007/05/microsoft_and_i.html
• Added archive https://web.archive.org/web/20070726181932/http://www.iunknown.com/2007/07/a-first-look-at.html to http://www.iunknown.com/2007/07/a-first-look-at.html
• Added archive https://web.archive.org/web/20070903213020/http://www.iunknown.com/2007/08/ironruby-on-rub.html to http://www.iunknown.com/2007/08/ironruby-on-rub.html
• Added archive https://web.archive.org/web/20080807064758/http://www.iunknown.com/2008/07/ironruby-at-oscon.html to http://www.iunknown.com/2008/07/ironruby-at-oscon.html
• Added archive https://web.archive.org/web/20090316034903/http://rubyforge.org/pipermail/ironruby-core/2008-August/002553.html to http://rubyforge.org/pipermail/ironruby-core/2008-August/002553.html
• Added archive https://web.archive.org/web/20090316034940/http://rubyforge.org/pipermail/ironruby-core/2008-September/002787.html to http://rubyforge.org/pipermail/ironruby-core/2008-September/002787.html
• Added archive https://web.archive.org/web/20090315051756/http://rubyforge.org/pipermail/ironruby-core/2009-January/003654.html to http://rubyforge.org/pipermail/ironruby-core/2009-January/003654.html
• Added archive https://web.archive.org/web/20120223233113/http://rubyforge.org/pipermail/ironruby-core/2009-May/004638.html to http://rubyforge.org/pipermail/ironruby-core/2009-May/004638.html
• Added archive https://web.archive.org/web/20080110142157/http://rubyconf2007.confreaks.com/d2t1p1_state_of_ironruby.html to http://rubyconf2007.confreaks.com/d2t1p1_state_of_ironruby.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 18:11, 16 November 2017 (UTC)