[erlang-questions] what does l/1 really do?

[Daniel Dormont]

2011/7/29 Håkan Mattsson <hm@REDACTED>

> http://www.erlang.org/doc/man/c.html#l-1
>
>
Good to know. In my defense, I couldn't find anything in the manual that
mentions "c" as the module to look in for those functions...

Any thoughts on my other question: if there are a variable-sized set of
dynamically-launched gen_fsm's using a particular module, assuming most/all
of them are idle or will be momentarily, is there a recommended way to
propagate a code upgrade across all of them?

dan


> /Håkan
>
> On Fri, Jul 29, 2011 at 4:27 PM, Daniel Dormont
> <dan@REDACTED> wrote:
> > While reading through some old discussion here or on TrapExit when I was
> > first trying to understand hot code loading, I ran across the shell
> command
> > l/1. Since then I've used it to good effect in patching a live system
> > (Ejabberd, specifically) with new or upgraded modules. But I'd like to
> > understand a little better what it's doing behind the scenes. I didn't
> see
> > any mention of it in the manual, and it's a little hard to Google for
> single
> > letters :), so I thought I'd ask here.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110729/0dc8e18a/attachment.htm>