Tomas Matousek wrote:
> This just means that something is calling add_builtin_type for wich we
> don't have implementation yet.
>
> Tomas
I know, fortunately it is just a warning, however,
I'm just speaking of standard gems,
That warning appears just after I execute the requires I'm mentioning.
This is a cross-post from Stack Overflow, but I haven't heard a peep there,
so I figured I'd try here:
I am playing around with the interop between C# and IronRuby. I have
noticed that if I define a property in Ruby using `attr_accessor`, it is
presented to C# as a property. If, on the other han
This just means that something is calling add_builtin_type for wich we don't
have implementation yet.
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Eduardo Blumenfeld
Sent: Monday, July 19, 2010 6:59 PM
To: i
Thanks, I'll fix it.
BTW: The code is based on CCI2 PE reader (http://ccimetadata.codeplex.com).
Tomas
-Original Message-
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Jb Evain
Sent: Wednesday, July 21, 2010 2:02 AM
To: ironruby-core
Hi Jimmy,
I've just released the first version of IronMock ( http://bit.ly/ironmock )
which uses 9 lines of embedded IronRuby to apply interfaces to objects at
runtime. It can be used for duck-typing any object, but there's also a
DynamicObject-based mocking class.
If you want a quote:
"I achiev
Hey,
Microsoft.Scripting.Metadata is being built with warnaserror, but it
contains a couple of issues that are not detected by csc, but that are
by dmcs, crashing the build. Here's a fix:
<<
diff --git a/Runtime/Microsoft.Scripting.Metadata/MemoryMapping.V2.cs
b/Runtime/Microsoft.Scripting.Me
