Looks good.
-Original Message-
From: Tomas Matousek
Sent: Sunday, October 26, 2008 10:16 PM
To: IronRuby External Code Reviewers
Cc: ironruby-core@rubyforge.org
Subject: Code Review: ido1
tfpt review "/shelveset:ido1;REDMOND\tomat"
Comment :
Implements Call, GetMember and Create dynami
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
If you save in "Western European (Windows) - Codepage 1252" from within Visual
Studio, you'll get the right result -- as long as you're not using any
characters with a codepoint greater than 127. And if you are, you're probably
better off anyway expressing this code point as an explicit set of
A lot of the work in 1.9 and 2.0 has gone to better unicode support. Most
string handling functions are now codepoint aware, and there is now the ability
for the source file to have an encoding attached to it.
Like Curt said, these are in flex, but they are spec'd in RubySpec, so they are
more
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
Is the DLR going to be fixed so that it properly supports Unicode
source files or is this an issue with IronRuby? If you attempt to
create a new Code File with Visual Studio 2008 and call it test.rb and
then execute it with:
ScriptRuntime runtime = IronRuby.Ruby.CreateRuntime();
runtime.ExecuteFi
With respect to conventions the dynamic languages are the first languages
that I've used that can actually depend on the casing (and pluralization) to
work right (think active record models). Now it's no longer part of the
"readability" factor of code but it can play an important part in how a DSL
The parenthesis do give an important clue, and luckily they are required for
calling a method with a constant identifier. As far as idioms and conventions
go, I don't know how much of an official convention (as much as a Ruby
convention is official) there is, but the few cases of capitalized met
On Sat, Oct 25, 2008 at 11:20 PM, Curt Hagenlocher <[EMAIL PROTECTED]>wrote:
> Now it turns out that method names are one of the places where Ruby doesn't
> draw this distinction, but I'd guess that many Ruby programmers look at any
> identifier starting with a capital letter and think "that's a c
12 matches
Mail list logo
