On Sat, Sep 6, 2008 at 12:04 AM, Curt Hagenlocher [EMAIL PROTECTED] wrote:
On Fri, Sep 5, 2008 at 5:16 PM, Dan Eloff [EMAIL PROTECTED] wrote:
I'm going to make a lot of work for you guys before the day is out :)
Maybe I should be posting these to the Issue Tracker? I'm just
concerned they will
Thanks! I've also created a bug report:
http://rubyforge.org/tracker/index.php?func=detailaid=21839group_id=4359a
tid=16798
This includes the irc.rb which I think IronRuby will be interested in
including in the IronRuby distribution as well..
I'll try to step through into this bug and
Okay, well I found two code problems in two IR implementations of
IExpressionSerializable:
/ironruby/Runtime/Calls/rubycallaction.cs CreateExpression() is passing the
wrong second Type parameter. It should be typeof(RubyCallSignature)
/ironruby/Runtime/Calls/rubycallsignature.cs
It's coming from the call stack - CompileLambda - AnalyzeLambda. The
LambdaExpression is ($scope, $language) = [Scope] but AnalyzeLambda
passes a null CompilerScope to VariableBinder.Bind. Somehow this same
VariableBinder is used during a ExpressionType.Call to:
//
// AST: MethodCallExpression
//
You'll probably want to track down where #globalScope is defined and make sure
the newly defined variable is getting added to the list of variables in a Scope
expression. If there's no scope expression you can just add one and give it
the original body the #globalScope var. Hopefully it's
I've posted comments on #7050 and #17355 demonstrating that the issues
are not yet fully resolved, but it occurs to me that it may go
unnoticed. Please could someone reopen those issues so that they are
not overlooked? In future would it be better if I open a new issue and
link to the old one?
