export_to (Was: Re: the OO metaphor)
Erik (Happi) Johansson
Mon Dec 4 12:16:46 CET 2000
> Håkan Mattsson wrote:
> > In order to manage code change without killing the process, fun's
> > should only be used for short tasks. By using a fun as the topmost
> > function in long lived server processes, you will effectively force
> > a kill of the process at next code change.
> No, not if the fun only does a tail-call to the server loop.
Unfortunately, one still needs to export a function in order to get
code change to work, but that has nothing to do with funs.
Still, code change is a counterexample to Richard's hypothesis that:
> There should now be no reason to export a function name
> that is not expected to be called from other modules.
(I should know better than writing emails early on Monday morning.)
More information about the erlang-questions