[<<][staapl][>>][..]
Sat May 23 13:27:15 CEST 2009

load/require interference

problem:
  target code generated by a module might be emptied. since a module
  won't be instantiated again, this will introduce dangling
  references..

crap.. it's not easy!

The real problem is that a module should not have an instantiation
side-effect.  Or, we should make it so that module code cannot be
erased. Or, 'empty' should clear the namespace.

Maybe the latter is the best approach.  That way modules will get
re-instantiated.

So.. Application development is separated in 2 parts:
  - kernel development (as self-contained .fm)
  - scripts that can accumulate

Upon reload the target should be cleared from the point that's marked
as the start of the script buffer.




[Reply][About]
[<<][staapl][>>][..]