[Ironruby-core] Using the console in IronRuby on Rails

Shay Friedman shay.friedman at gmail.com
Fri Oct 30 18:26:49 EDT 2009


Thanks guys!

On Fri, Oct 30, 2009 at 10:22 PM, Jimmy Schementi <
Jimmy.Schementi at microsoft.com> wrote:

> Sorry, this is a patch I missed in the docs (
> http://ironruby.net/Documentation/Real_Ruby_Applications/Rails#console).
> This behavior hasn’t changed in Rails, and I fixed it in the past without
> patch IronRuby, so I would suggest not patching IronRuby now to fix it. I’ll
> figure out what the exact patch to Rails was and post it to the
> documentation.
>
>
>
> *From:* ironruby-core-bounces at rubyforge.org [mailto:
> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Jim Deville
> *Sent:* Friday, October 30, 2009 12:57 PM
>
> *To:* ironruby-core at rubyforge.org
> *Subject:* Re: [Ironruby-core] Using the console in IronRuby on Rails
>
>
>
> I would like to see if MRI uses PATHEXT in this case, but I think from
> talking with Tomas, that it doesn’t.
>
>
>
> *From:* ironruby-core-bounces at rubyforge.org [mailto:
> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Shri Borde
> *Sent:* Friday, October 30, 2009 12:14 PM
> *To:* ironruby-core at rubyforge.org
> *Subject:* Re: [Ironruby-core] Using the console in IronRuby on Rails
>
>
>
> You can add a RubySpec spec for it to see the details of the specific Ruby
> API. Then if MRI and IronRuby both have the same behavior for the spec, your
> patch would be correct. Ie. You can use TDD to figure out the right
> behavior.
>
>
>
> *From:* ironruby-core-bounces at rubyforge.org [mailto:
> ironruby-core-bounces at rubyforge.org] *On Behalf Of *Shay Friedman
> *Sent:* Friday, October 30, 2009 11:50 AM
> *To:* ironruby-core
> *Subject:* [Ironruby-core] Using the console in IronRuby on Rails
>
>
>
> Hi there,
>
> I tried to use the Ruby on Rails console with IronRuby on an application
> I'm building by executing "ir script/console". Doing so ended up with an
> exception from RubyProcess.CreateProcess.
>
> I debugged and found out that RoR tries to execute irb.bat which is MRI's,
> so I modified rails-2.3.3\lib\commands\console.rb to point to iirb.bat
> instead. That didn't work as well.
> I continued and discovered that RubyProcess doesn't consider bat files as
> executables. I don't know if it's on purpose but in order to fix the
> problem, I added the bat extension to the valid executable extension list
> and set the full path of iirb.bat in rails' console.rb file.
>
> Am I doing something wrong or is my little patch correct?
>
> Thanks,
> Shay.
>
> --
> --------------------------------------------------
> Shay Friedman
> Author of IronRuby Unleashed
> http://www.IronShay.com
> Follow me: http://twitter.com/ironshay
>
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core
>
>


-- 
--------------------------------------------------
Shay Friedman
Author of IronRuby Unleashed
http://www.IronShay.com
Follow me: http://twitter.com/ironshay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20091031/05c4505c/attachment-0001.html>


More information about the Ironruby-core mailing list