Mon Nov 3 22:32:09 CET 2014
A user of PropEr (http://proper.softlab.ntua.gr/) reported that he was
not able to use the erlang:timestamp() type as generator. (I.e. be able
to generate random time stamp values using the existing mechanisms that
The culprit was traced to function code:get_object_code/1 which returns
'error' for the 'erlang' module, instead of returning a tuple with its
binary data object and beam filename, as one would expect.
While for pretty much all other modules, one gets:
Is there a reason for this discrepancy?
There is a variety of tools that needs to be able to manipulate the
object code or extract information from the abstract code of modules,
such as the list of their exported types, and there needs to be some
(preferably simple) way of getting access to this information.
In investigating further the issue, I discovered that the problem can be
fixed if one manually adds the erts/preloaded/erl dir in the code path.
But in my opinion, having to do this is unnecessarily complicated,
possibly error prone and breaks the principle of least astonishment.
So, I can ask my question differently: Can we please have the preloaded
modules in the code path, since they arguably are there?
More information about the erlang-questions