aef4efb959
The result isn't an identical binary to before, and it segfaults when
run. But it's bugfix seven.
A couple of places where we make .subx files a little more strict:
a) All .subx files must define a data segment. Even if they have no
data.
b) All .subx files must define an `Entry` label for the binary to start
at. Earlier we used to default to the start of the code label. That's
not too hard to add; we'd just need to:
i) rename `get` to `get-or-abort`
ii) clone a third variant of `get-or-insert` called `get` that returns
null if the key is not found.
iii) use `get` rather than `get-or-abort` when looking up the `Entry`
label.
|
||
|---|---|---|
| .. | ||
| assort | ||
| assort.subx | ||
| crenshaw2-1 | ||
| crenshaw2-1.subx | ||
| crenshaw2-1b | ||
| crenshaw2-1b.subx | ||
| dquotes | ||
| dquotes.subx | ||
| factorial | ||
| factorial.subx | ||
| handle | ||
| handle.subx | ||
| hex | ||
| hex.subx | ||
| pack | ||
| pack.subx | ||
| Readme.md | ||
| subx-common.subx | ||
| survey | ||
| survey.subx | ||
Larger programs than in the subx/examples/ subdirectory, combining the techniques demonstrated there.