Sounds good.
JD
> -Original Message-
> From: Shri Borde
> Sent: Thursday, March 26, 2009 3:00 PM
> To: Jim Deville; Tomas Matousek; IronRuby External Code Reviewers
> Cc: ironruby-core@rubyforge.org
> Subject: RE: CR: IronRuby tests for IDMOP, and ir_wrap.cmd
>
> I will add comments. The
I will add comments. The code should be as shown. The reason y exists for now
is to document the expected result. However, because the IDMOP support isn't
baked, IronRuby produces "buggyResult" today. Say 1+2 give 300 today. In that
case, I have added "AreEqual(1+2, 3, 300) to document what the
+[DebuggerHiddenAttribute]
+internal void AreEqualBug(object x, object y, object buggyResult) {
+AreEqual(x, buggyResult);
+}
+
+[DebuggerHiddenAttribute]
+internal void AreEqualBug(Action f, object y) where T : Exception {
+AssertExce
DLR interop tests look good.
Tomas
-Original Message-
From: Shri Borde
Sent: Thursday, March 26, 2009 1:03 PM
To: IronRuby External Code Reviewers
Cc: ironruby-core@rubyforge.org
Subject: CR: IronRuby tests for IDMOP, and ir_wrap.cmd
tfpt review "/shelveset:iridmop;REDMOND\sborde"
tfpt review "/shelveset:iridmop;REDMOND\sborde"
Comment :
Adding unit tests for Ruby's IDynamicMetaObjectProvider support. Failing
scenarios are tagged with AreEqualBug and AssertExceptionThrownBug
Added Languages\Ruby\Scripts\ir_wrap.cmd as the replacement for
Test\Scripts\ir.cmd whic
