[erlang-questions] Loading code generated on the fly

[Robert Virding]

2008/9/27 Attila Babo <babo.online@REDACTED>

> We experienced in a long running production environment that generated
> code are sometimes unloaded, our current workaround is to check its
> presence and reload it from a database if needed. Is there a way to
> force to keep it in cache? A possibility to create a dummy process to
> keep a single reference to the module all way long. Is there a better
> way?


Sorry I have absolutely no idea what the problem is and how to solve it. How
do you mean unload? Like suddenly it is not there and can't be called? I
personally think that is very strange if erlang decides to unload code,
generated or otherwise, all by itself. I would raise this as a separate
question so that more people see it.

Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080927/4d0655c5/attachment.htm>