Tue May 13 19:06:25 CEST 2008
load vs. require
the next problem is load vs req.. should i keep load? in the current
.f files a lot is done using late binding: require the includer to
specify some words.. this goes against the bottom-up module
approach. how to solve it?
finding a decent solution for this late binding is quite important:
code generation is heavily parameterized: it's inconvenient to have to
specify.. i'm already using this trick in the core, so why not in the
libs.. the only problem is: it can generate run-time errors.