Currently atoms are independent of environment (ErlNifEnv). That is, you
can cache atoms by storing them in static variables as done in crypto.c.
This is an undocumented feature however.
To compensate for future possible introduction of atom-GC I have thought
"Atoms created in load/upgrade callbacks are static and can be used in
Lukas Larsson wrote:_______________________________________________
> If I understand you correctly the answer is yes.
> I think the crypto implementation does exactly this and since
> On Fri, May 4, 2012 at 3:22 PM, Max Lapshin <max.laps...@gmail.com> wrote:
>> Is there a way to cache atoms in NIF?
>> Is it ok just to store in static variable result of enif_make_atom ?
erlang-questions mailing list
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.