44ee578a3a
This adds support for `include as <identifier>` type statements which in addition to pulling in any defined resources, it also makes the contents of the scope of the class available to the scope of the include statement, but prefixed by the identifier specified. This makes passing data between scopes much more powerful, and it also allows classes to return useful classes for subsequent use. This also improves the SetScope procedure and adds to the Ordering stage. It's unclear if the current Ordering stage can handle all code, or if there exist corner-cases which are valid code, but which would produce a wrong or imprecise topological sort. Some extraneous scoping bugs still exist, which expose certain variables that we should not depend on in future code. Co-authored-by: Samuel Gélineau <gelisam@gmail.com>
43 lines
627 B
Plaintext
43 lines
627 B
Plaintext
-- main.mcl --
|
|
class c0($b) {
|
|
test "t1" {}
|
|
if $b {
|
|
test "t2" {}
|
|
} else {
|
|
test "t3" {}
|
|
}
|
|
func f0() {
|
|
if $b {
|
|
"hello"
|
|
} else {
|
|
"goodbye"
|
|
}
|
|
}
|
|
}
|
|
class c1($b) {
|
|
test "t4" {}
|
|
if $b {
|
|
test "t5" {}
|
|
} else {
|
|
test "t6" {}
|
|
}
|
|
include c0($b) as i0
|
|
func f1() { i0.f0() }
|
|
}
|
|
include c1(true) as i1
|
|
include c1(false) as i2
|
|
|
|
test i1.f1() {}
|
|
test i2.f1() {}
|
|
test i1.i0.f0() {} # I think these might work directly too. Do we want them to?
|
|
test i2.i0.f0() {}
|
|
-- OUTPUT --
|
|
Vertex: test[goodbye]
|
|
Vertex: test[hello]
|
|
Vertex: test[t1]
|
|
Vertex: test[t2]
|
|
Vertex: test[t3]
|
|
Vertex: test[t4]
|
|
Vertex: test[t5]
|
|
Vertex: test[t6]
|