engines: use `callsite.msignature` in ASuperExpr
authorJean Privat <jean@pryen.org>
Mon, 12 May 2014 17:13:32 +0000 (13:13 -0400)
committerJean Privat <jean@pryen.org>
Tue, 13 May 2014 10:01:31 +0000 (06:01 -0400)
instead of `callsite.mproperty.intro.msignature`

This will also be usefull with new constructors when
the signature between the callsite and the propdef differs

Signed-off-by: Jean Privat <jean@pryen.org>

src/abstract_compiler.nit
src/naive_interpreter.nit

index 9b789b6..76d2e6c 100644 (file)
@@ -2565,7 +2565,7 @@ redef class ASuperExpr
                if callsite != null then
                        # Add additionnals arguments for the super init call
                        if args.length == 1 then
-                               for i in [0..callsite.mproperty.intro.msignature.arity[ do
+                               for i in [0..callsite.msignature.arity[ do
                                        args.add(v.frame.arguments[i+1])
                                end
                        end
index f53be09..24ed8d5 100644 (file)
@@ -1560,7 +1560,7 @@ redef class ASuperExpr
                if callsite != null then
                        # Add additionnals arguments for the super init call
                        if args.length == 1 then
-                               for i in [0..callsite.mproperty.intro.msignature.arity[ do
+                               for i in [0..callsite.msignature.arity[ do
                                        args.add(v.frame.arguments[i+1])
                                end
                        end