Code changing

[Klacke]

 > change, but in R4B and OSE they do. Your only bet in Open Source (apart
 > from waiting for the next release) is either avoiding funs in your state,
 > or "recreating" them during code change (which is not always practical.)
 > 

It's not the case that Luke can avoid to use Funs in the state.
The etk library uses Funs in the state and all of us etk users
are stuck with that. We'll just have to wait for the next release.


/klacke