You can switch to 1.9 compat mode by passing -19 argument on command line.
Tomas
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Milker
Sent: Sunday, October 26, 2008 1:57 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Unicode Source
On Sun, Oct 26, 2008 at 3:17 PM, Jim Deville <[EMAIL PROTECTED]> wrote:
>
> If you are able to solve this with an extension method, then it looks likely
> that any VS integration work for IRb will take care of that. As it is, I use
> GVim for most of my Ruby coding these days. :)
I use ViEmu for
ruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Unicode Source Files
Why so rigorous? I understand the need to maintain compatibility but
this effectively eliminates Visual Studio as an editor for .rb files,
without some kind of clunky build mechanism. I guess I will just use
an extension method
ROTECTED]>
Sent: October 26, 2008 12:08 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Unicode Source Files
Here is the extension method I am using if anyone else is interested:
public static object ExecuteUnicodeFile( this ScriptRuntime rt, string
filename )
{
st
Here is the extension method I am using if anyone else is interested:
public static object ExecuteUnicodeFile( this ScriptRuntime rt, string
filename )
{
string rbCode;
// OpenText will strip the BOM and keep the Unicode intact
using( var rdr = File.OpenText( filename ) )
{
Why so rigorous? I understand the need to maintain compatibility but
this effectively eliminates Visual Studio as an editor for .rb files,
without some kind of clunky build mechanism. I guess I will just use
an extension method to get around the behavior for the time being.
>From the things I ha
We do this for compatibility with Ruby 1.8.6, though as you can see, we don't
have the error message quite right:
PS F:\> C:\ruby\bin\ruby.exe x.rb
x.rb:1: Invalid char `\377' in expression
x.rb:1: Invalid char `\376' in expression
:)
I believe you'll need to save as UTF-8 and then manually str
