export_to (Was: Re: the OO metaphor)

Hakan Mattsson hakan@REDACTED
Mon Dec 4 10:35:17 CET 2000

On Fri, 1 Dec 2000, Richard Carlsson wrote:

Richard> This should not be needed, since you can nowadays write:
Richard> 	spawn(fun () -> my_nonexported function(X1, ..., Xn) end)
Richard> There should now be no reason to export a function name that is not
Richard> expected to be called from other modules. (Counterexamples, anyone?)

What about code change?

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.


More information about the erlang-questions mailing list