Age | Commit message (Collapse) | Author |
|
In the transition from SGML to XML (several releases ago),
bugs were introduced in the documentation, for instance
"\n" replaced by newlines. Correct those bugs.
Also correct double backslashes. They seem to have been introduced very
early in the development of OTP. According to Lars they "solved" a bug
in the generation of HTML &c. Now that standard tools are used instead
of docbuilder, the bug has become visible.
|
|
The MIB compiler in the snmp applications formats its warnings slightly
differently, so we'll need to update the regexp that should match the
expected output.
|
|
short-circuit expressions in guards.
|
|
* ks/dialyzer-wx-fix:
dialyzer: make -wx always start the SMP emulator
|
|
* bg/make_stub_module-fix:
Fix glitches when native code modules are used
|
|
* bg/on_load-types:
Add type information for on_load
|
|
* egil/readme-debug-emulator:
README: Add build instructions for a debug-enabled emulator
|
|
* ng/readme:
Clean up formatting issues in the README
|
|
Note that although the copyright markers may seem ugly,
they must be there to facilitate automatic updating of
the copyright text.
|
|
|
|
The erlang:make_stub_module/3 BIF (which is only used for
loading native code) does not zero the word that points out
an on_load routine (if any). As that word most proably will
contain a non-zero value, the erlang:module_loaded/1 BIF will
think that the module has an on_load routine which has not
returned and will always return 'false'. That in turns causes
various problems for the native code test cases.
|
|
The wx application will only work in the SMP emulator,
so the -wx option for 'dialyzer' must force the -smp
option when starting the emulator.
Make sure that -wx in *any* position on the command
line (not only as the first argument) forces the
SMP emulator.
|
|
* refs/remotes/origin/dgud/array_tests:
Added more tests for array:reset/2.
|
|
The on_load feature introduced in R13B03 adds two new internal
BIFs and extends the return value of erlang:load_module/2.
|
|
Code coverage was bad for my new optimizations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|