[erlang-questions] Rationale behind ets:lookup_element/3 behavior

Mihai Balea <>
Fri Aug 8 20:38:20 CEST 2008

Hi all,

I have been hit by a strange behavior when using ets:lookup_element/3:
Normally, when the Key is not found, I would expect that the function  
would return [].  Indeed, this is what happens with ets:lookup/2 .  
However, ets:lookup_element/3 throws a badarg exception.  While this  
is documented, it seems.... well, inconsistent. Can anybody clue me in  
as to the rationale behind this behavior?


More information about the erlang-questions mailing list