Age | Commit message (Collapse) | Author |
|
* bw/tv-render-fix:
tv: Allow table viewer to display refs, ports and small binaries
OTP-9153
|
|
* bjorn/compiler/bin-size-bug/OTP-9134:
v3_core: Fix variable incorrectly unbound after binary match
v3_core: Fix style and indentation
|
|
* sg/fix-diskless-booted-relup:
Remove traces of release_handler reading from filesystem when it has
Masters list
OTP-9142
|
|
* cg/fix-sizeof-array-arg:
Fix using sizeof() for array given as function argument
OTP-9151
|
|
* siri/reltool/skip-xref-test-when-debug/OTP-9133:
Skip reltool_app_SUITE:undef_funcs on debug compiled emulator
|
|
* siri/reltool/app_file-option/OTP-9135:
Allow app_file option to be keep | strip | all, as documented
|
|
* ia/public_key/encode-decode-ssh/OTP-9144:
Implemented encode/decode support for ssh public key files
|
|
|
|
In the following code:
m(<<Sz:8,_:Sz/binary>>) ->
Sz = wrong.
the Sz variable is supposed to be bound in the function header and the
matching "Sz = wrong" should cause a badarg exception. But what
happens is that the Sz variables seems to be unbound and the matching
succeds and the m/1 function returns 'wrong'.
If the Sz variable is used directly (not matched), it will have
the expected value. Thus the following code:
m(<<Sz:8,_:Sz/binary>>) ->
Sz.
will correctly return the value of Sz that was matched out from
the binary.
Reported-by: Bernard Duggan
|
|
|
|
The default value 'undefined' was added to records field types in such
a way that the result was not always a well-formed type. This bug has
been fixed.
---
erl_pp has since OTP-8150 formatted types so that 'undefined' was
removed from union types assigned to record fields. Since one cannot
distinguish between 'undefined' added by the parser or supplied by the
user, a side effect was that user supplied 'undefined's were also
removed.
Now the pretty printer shows 'undefined' even if added by the parser.
This is a minor issue.
|
|
This is the correction of the bug not allowing the values 'strip' or
'all' for the app_file option in reltool.
|
|
list
There are a couple of places in release_handler and release_handler_1
that assumed it has a disk to read from, which in the case of an
erl_prim_loader Loader other than efile is not necessarily true
Add check_paths/2 to do the equivalent of check_path/1 for when there
is a Masters list
Change get_vsn to no longer get sent File paths but instead use the
Bin since beam_lib:version being sent a file path causes it to read
the local file system
Add get_current_vsn/1 as an equivalent to
beam_lib:version(code:which(Mod)), but using erl_prim_loader:get_file
instead of reading from local file system
|
|
|
|
|
|
|
|
* nick/CORBA/avoid_warnings/OTP-9050:
Corrected type of action in release notes.
Corrected version in release notes file.
Conflicts:
lib/cosProperty/doc/src/notes.xml
|
|
|
|
|
|
|
|
* pan/doc_link_corrections/OTP-9112:
Remove link_check warnings re httpc.xml,sys.xml and unicode.xml
Change io.xml so that html anchors gets generated for all arities
|
|
* sa/dialyzer-missing-spec:
Add spec to dialyzer_cl_parse:get_lib_dir/1
OTP-9129
|
|
* ks/kernel-dialyzer-cleanups:
Add spec for function that does not return
Strenghen spec
Introduce types to avoid duplication in specs
Add specs for functions that do not return
Add specs for behaviour callbacks
Simplify two specs
OTP-9127
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Applies to the specification of the return value of a function.
|
|
|
|
|
|
|
|
|
|
|
|
* ay/precisionfix/OTP-8989:
Fix ~F.Fs bug, add testcase and improve documentation
io_lib_format string precision fix
|
|
|
|
It is now possible to use Erlang specifications and types in EDoc
documentation. Erlang specifications and types will be used unless
there is also a function specification (@spec) or a type alias (@type)
with the same name. In the current implementation the placement of
-spec matters: it should be placed where the @spec would otherwise
have been placed.
Not all Erlang types are included in the documentation, but only those
exported by some export_type declaration or used by some documented
Erlang specification (-spec).
There is currently no support for overloaded Erlang specifications.
The syntax definitions of EDoc have been augmented to cope with most
of the Erlang types. (But we recommend that Erlang types should be
used instead.)
edoc:read_source() takes one new option, report_missing_types.
edoc_layout:module() takes one new option, pretty_printer.
|
|
* lukas/common_test/suite_callback/OTP-8851:
Update init_per_suite to not crash when there is no suite/0
Update links info in ct_hooks to point to the right place
Update ct_hooks to fail gracefully when a hook is entered incorrectly in suite/0
|
|
|
|
|
|
|
|
* mh/emacs-indent-variables-are-safe:
Declare indentation options as "safe" in erlang-mode for Emacs
OTP-9122
|
|
* ks/reltool-spec-fixes:
Fix erroneous types
Eliminate two dialyzer warnings
Cleanup
Code cleanups and simplifications
Fix a bug in the calculation of circular dependencies
Use lists:foreach/2 when the return is not needed
Put files alphabetically
Fix two erroneous specs of reltool.erl
OTP-9120
|
|
Emacs has a facility for setting options on a per-file basis based on
comments in the source file. By default, all options are considered
"unsafe", and the user is queried before the variable is set. This
patch declares the variables erlang-indent-level, erlang-indent-guard
and erlang-argument-indent to be safe, if the value specified in the
source file is valid.
Such declarations usually look like this:
%% -*- erlang-indent-level: 2 -*-
and appear on the first line of the file.
|
|
* aronisstav/dialyzer/dialyzer_tests/OTP-9116:
Increase timetrap of options1 suite
Write output_plt even when plt_check is ok
Create plt with erts, kernel and stdlib only
Update test results as they currently appear in dev
Major restructure of dialyzer's testsuite
Add 'apps' option to the erlang interface
Update spec file to work with new common test structure
Test suites for Dialyzer
|
|
|
|
"When I run mnesia:first on an empty fragmented table, it tries to
access the fragment with the number one beyond the maximum. In the
sample code below, I create a table with two fragments, 'foo' and
'foo_frag2', but mnesia tries to access 'foo_frag3':"
|