| Age | Commit message (Collapse) | Author |
|---|
|
* maint:
[xmerl] Remove faulty throws
[xmerl] Fix XML "well-formedness" bug i SAX parser
[xmerl] Correct bug handling multiple documents on a stream
stdlib: Improve pretty-printing of terms with maps
Conflicts:
lib/stdlib/test/io_SUITE.erl
|
|
|
|
Documentation: fix link to erlang(3) man page
|
|
* hasse/stdlib/fix_pretty_maps/OTP-14175:
stdlib: Improve pretty-printing of terms with maps
|
|
* lars/xmerl/sax-parser-multi-doc-problem:
[xmerl] Remove faulty throws
[xmerl] Fix XML "well-formedness" bug i SAX parser
[xmerl] Correct bug handling multiple documents on a stream
OTP-14211
OTP-14213
|
|
* siri/ct/get_dirs_from_testspec/OTP-14132:
[ct] Add ct_testspec:get_tests/1
|
|
|
|
Changed the XML Sax parser behaviour so it returns an error
if there are something more in the file after the the
matching document. If one using the xmerl_sax_parser:stream()
a rest is allowed which then can be sent to a new call of
xmerl_sax_parser:stream() to parse next document.
This is done to be compliant with XML conformance tests.
|
|
Change how to interpret end of document to comply with Tim Brays
comment on the standard. This makes it possible to handle more
than one doc on a stream, the standard makes it impossible to
know when the document is ended without waiting for the next
document (and not always even that).
Tim Brays comment about the trailing "Misc" rule:
The fact that you're allowed some trailing junk after the root
element, I decided (but unfortunately too late) is a real design
error in XML. If I'm writing a network client, I'm probably going
to close the link as soon as a I see the root element end-tag, and
not depend on the other end closing it down properly.
Furthermore, if I want to send a succession of XML documents over
a network link, if I find a processing instruction after a root
element, is it a trailer on the previous document, or part of the
prolog of the next?
|
|
|
|
into maint
* legoscia/erl_interface/doc-no-tuple-funs/PR-1343/OTP-14233:
Documentation: tuple funs are unsupported
|
|
As of committing this branch maps:fold/3 calls maps:to_list/1, which
means that the time and memory needed for printing maps is not always
proportional to the size of the generated deep list of characters.
|
|
* hasse/dialyzer/correct_tests:
dialyzer: Correct test cases after removal of erlang:hash/2
|
|
|
|
* rickard/magic-references-fixes:
Fix driver monitor implementation
Handle magic refs in db_cleanup_offheap_comp()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I don't see why this should point to process_flag/2. Let's make it not
do that.
|
|
An error report on ssh_cli pointed to a usage of erlang:iolist_size/1. It is replaced by a specialized function.
|
|
|
|
* bjorn/fix-make_preload:
Teach make_preload to handle the new 'AtU8' chunk
|
|
26b59dfe67 introduced the new 'AtU8' chunk to support
Unicode atoms.
make_preload strips the pre-loaded BEAM files so that they
only contain essential chunks. It expects to find the old
'Atom' chunk.
Teach make_preload to read the new 'AtU8' chunk instead of the old
chunk. Also produce a nice error message if someone by mistake
compiles the pre-loaded modules with an OTP 19 compiler.
|
|
machines
|
|
Conflicts:
lib/ssh/test/ssh_sftpd_SUITE.erl
|
|
Conflicts:
lib/ssh/test/ssh_sftpd_SUITE.erl
|
|
hans/ssh/sftpd_fixes/OTP-14225
|
|
* bjorn/asn1/clean-up-asn1ct_gen:
asn1ct_gen: Clean up handling of dispatch generation
Package abstract code in a record for code generation
asn1ct_gen: Polish the file header
asn1ct_gen: Clean up generation of .hrl file header
asn1ct_gen: Clean up generation records in .hrl file
asn1ct_gen: Clean up generation of -export directives
asn1ct_gen: Clean up generation of values
|
|
|
|
|
|
|
|
|
|
maint
|
|
|
|
* sverker/enif_send-noproc-fix:
erts: Fix enif_send from noproc and no msg_env
|
|
|
|
* sverker/include-module-literal-size:
erts: Add size of literals to module code size
|
|
|
|
* sverker/round-bug/OTP-14227:
erts: Fix round/1 for large floats
|
|
Update erl_tar to support PAX format (redux)
OTP-14226
|
|
This commit introduces the following key changes:
- Support for reading tar archives in formats currently in common use,
such as v7, STAR, USTAR, PAX, and GNU tar's extensions to the
STAR/USTAR format.
- Support for writing PAX archives, only when necessary, using USTAR
when possible for greater portability.
These changes result in lifting of some prior restrictions:
- Support for reading archives produced by modern tar implementations
when other restrictions described below are present.
- Support for filenames which exceed 100 bytes in length, or paths which
exceed 255 bytes (see USTAR format specification for more details on
this restriction).
- Support for filenames of arbitrary length
- Support for unicode metadata (the previous behaviour of erl_tar was
actually violating the spec, by writing unicode-encoded data to fields
which are defined to be 7-bit ASCII, even though this technically
worked when using erl_tar at source and destination, it may not have
worked with other tar utilities, and this implementation now conforms
to the spec).
- Support for uid/gid values which cannot be converted to octal
integers.
|
|
|
|
For now, do the packaging before call asn1ct_gen:pgen().
|
|
|
|
|
|
* lars/xmerl/standard-namespace-problem/OTP-14139:
[xmerl] Correct handling of implicit XML namespace
|
