Menu

#1 Ensemble dispatch via cmd resolver does not honour method combination (next)

2.1.1
closed
ssoberni
2017-08-08
2017-06-11
ssoberni
No
nx::Class create A {
    :method "i s" args {
    next
    return [current class]
    }
}

nx::Class create B  -superclasses A {
    :public method "i s" args {
    return [list [current class] {*}[next]]
    }
    :create b
}

? {b eval { :i s }} "::B"; # shouldn't that be "::B ::A" as well?
? {b eval { : i s }} "::B ::A"
? {b i s} "::B ::A"

the dispatch via ":i is" and ": i s" should not show any difference.

Discussion

  • ssoberni

    ssoberni - 2017-08-08
    • status: open --> closed
    • Milestone: 2.1.0 --> 2.1.1
     
  • ssoberni

    ssoberni - 2017-08-08

    Fix in commit 404b559

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.