[erlang-bugs] erlang module not in sticky dir?

[Björn Gustavsson]

On Thu, May 8, 2014 at 11:59 AM, Stavros Aronis <aronisstav@REDACTED> wrote:
> Somewhat related (posted earlier at
> http://erlang.org/pipermail/erlang-bugs/2014-April/004300.html )
>
> $ erl
> Erlang/OTP 17 [erts-6.0] [source-07b8f44] [64-bit] [smp:8:8]
> [async-threads:10] [hipe] [kernel-poll:false]
>
> Eshell V6.0  (abort with ^G)
> 1> erlang:is_builtin(erlang,apply,3).
> false
>

I am not sure what to do about this one.
It is not really a BIF. It is defined in the
erlang module like this:

apply(Mod, Name, Args) ->
    erlang:apply(Mod, Name, Args).

That may seem a little bit strange, but it
works because the loader replaces the call
to erlang:apply/3 with an instruction.

Perhaps we should call it a built-in. After
all, it is implemented in C, but not in the same
way as (for example) is_list/1.

Any suggestions?

/Bjorn

-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB