I just sent out a pull request, here's the diff to fix the error:

 Merlin/Main/Languages/Ruby/Ruby/Runtime/BinaryEncoding.cs

@@ -30,7 +30,8 @@ namespace IronRuby.Runtime {
         // TODO: remove
         public static readonly Encoding/*!*/ Obsolete = Instance;

- private BinaryEncoding() {
+ private BinaryEncoding():base(0) {
+
        }
         public override int GetByteCount(char[]/*!*/ chars, int index, int
count) {


On Tue, Feb 10, 2009 at 9:27 AM, Michael Letterle <
[email protected]> wrote:

> I have this bug fixed in my linux/mono branch.  File a bug (if there isn't
> one already) and I'll submit my patch to it.
>
> On Mon, Feb 9, 2009 at 7:48 PM, Thibaut Barrère <[email protected]
> > wrote:
>
>> Hi,
>> two things:
>>
>> - I'm sharing in case it's useful to someone else: I pushed some rake
>> tasks here http://github.com/thbar/ironruby-labs/tree/master . I'm using
>> it to download the DLR nightly to my Mac, patch ir.exe.config and launch
>> mono ir.exe. I'll add more things there as I go (including UI,
>> experimentations etc).
>>
>> - is "mono Release/ir.exe -D somefile.rb" supposed to work with Mono 2.2
>> and the latest DLR build (10584) ? It seems that I'm facing the issue Ivan
>> reported a while back:
>>
>> Macintosh:ironruby-labs thbar$ mono Release/ir.exe -D ui/ui.rb
>> mscorlib:0:in `set_Fallback': Argument cannot be null.
>> (System::ArgumentNullException)
>> from mscorlib:0:in `.ctor'
>>  from mscorlib:0:in `GetDecoder'
>> from mscorlib:0:in `Initialize'
>> from mscorlib:0:in `.ctor'
>>  from mscorlib:0:in `.ctor'
>>
>> cheers,
>>
>> -- Thibaut
>>
>> _______________________________________________
>> Ironruby-core mailing list
>> [email protected]
>> http://rubyforge.org/mailman/listinfo/ironruby-core
>>
>>
>
>
> --
> Michael Letterle
> IronRuby MVP
> http://blog.prokrams.com
>
>
>


-- 
Michael Letterle
IronRuby MVP
http://blog.prokrams.com
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core

Reply via email to