| Age | Commit message (Collapse) | Author |
|---|
|
* ms/file-exclusive-mode:
Update preloaded modules
Support opening files in exclusive mode
OTP-8670 ms/file-exclusive-mode
There is a new option 'exclusive' to file:open/2 that uses the OS O_EXCL
flag where supported to open the file in exclusive mode.
|
|
* cb/emacs-eunit-run-recent:
erlang-eunit: remove runtime dependency on cl package
Add Emacs EUnit feature: run recent
Add Emacs EUnit feature: auto-save
|
|
* kj/emacs-eunit-run-current-test-with-cover:
erlang-eunit: Optionally run code coverage analysis during eunit tests
erlang-eunit: Made alternative locations of files more flexible
|
|
|
|
* ia/ssl_many_handshake_packages_at_once:
Fixed handling of several ssl/tls packets arriving at the same time.
OTP-8679 ia/ssl_many_handshake_packages_at_once
|
|
|
|
|
|
|
|
OTP-8564: Update deeprication status.
OTP-8573: Inets mod_alias URL rewrite.
|
|
Follow the GNU recommendation of not introducing runtime
dependencies on the Common Lisp package in ELisp packages
that will be distributed for widespread use.
In practice this means it's ok to use cl macros but not
functions.
|
|
This determines the most recent invocation of EUnit and runs it
again -- whether one test or all tests in a module were run (and
if all a module's tests were run, whether cover compilation was
involved). This can be especially handy when one test is being
run repeatedly, eliminating the need to position the cursor in
the desired test just to run it.
Default keybinding: C-c C-e l
|
|
If the variable 'erlang-eunit-autosave' is non-nil, buffers will be
automatically saved just before running tests -- the "Do you want
to save?" prompt will be inhibited. This can be useful, reducing the
save-compile-load-test cycle to just one keychord.
|
|
Add a number of features to the emacs mode which make it easier to
work with eunit test cases while keeping track of code coverage.
* C-cC-ec:
Compile the module under test for code coverage analysis, run tests
and show the results of the coverage analysis in a new buffer.
* C-c-C-ev:
Compile the current module for code coverage analysis.
* C-cC-ea:
Show the results of the coverage analysis in a new buffer.
|
|
Previously there were only two options: either the EUnit test file was
placed directly within the test directory or within the same directory
as the source file. Now a list of candidate locations are supported.
This way more than two alternative locations are supported as well as
arbitrarily deep directory structures (i.e. test/eunit/x_tests.erl).
The default behaviour is still the same, but it's possible to specify
locations by setting the following two variables:
erlang-eunit-src-candidate-dirs
erlang-eunit-test-candidate-dirs
|
|
|
|
In commit 1858cb81391d2bce29b4b7620574ca60128cebf7, erl_expand_records
started to optimize is_record/2 in guards by replacing it with
pattern matching (if possible).
Unfortunately, dialyzer will no longer see the code before the
optimization, so any warnings produced in code such as:
case ExprNotProducingRecord#rec{} of
X when is_record(X, rec, N) -> ...
will refer to the optimized code and not the source code,
which is confusing for the user.
Introduce the no_is_record_optimization option for turning off
the optimization and use it in dialyzer.
Reported-by: Kostis Sagonas
|
|
* uw/mnesia-overload:
Enable continuous monitoring of mnesia overload status
|
|
* uw/mnesia-schema-merge:
remove debug printout and accidental variable name reuse
Allow a user_defined function to wrap mnesia_schema:merge_schema()
|
|
Add an option that atomically tests for the existence of a file and
creates it if the file does not exist, by passing the O_EXCL flag
to open() on Unix and CREATE_NEW flag on Windows. Support for O_EXCL
varies across platforms and filesystems.
{ok, Fd} = file:open("/tmp/foo", [write,exclusive]),
{error, eexist} = file:open("/tmp/foo", [write,exclusive]).
|
|
|
|
* ks/dialyzer:
dialyzer: Build the PLT even if there are unresolved remote types
proplists: Export the type property()
erl_lint: Issue warnings for undefined exported types
Minor fix in a print message
Add handling of unknown types
Add declaration for exported types
Add types and specs; performed some cleanups also
erl_scan: Add declarations for exported types
stdlib: Add declarations for exported types
hipe: Add declarations for exported types
compiler: Add declarations for exported types
syntax_tools: Add declarations for exported types
kernel: Add declaration for exported types
Support -export_type() in dialyzer and erl_types
Add infrastructure for the -export_type() attribute
OTP-8678 ks/dialyzer
|
|
OTP-8561: Performance improvments in megaco_config:conn_info
OTP-8627: Fix flex lib(s) installation
OTP-8634: Pending counter raise condition
|
|
This was broken during a refactoring of the code.
|
|
|
|
New NIF features:
Send messages from a NIF, or from thread created by NIF, to any local
process (enif_send)
Store terms between NIF calls (enif_alloc_env, enif_make_copy)
Create binary terms with user defined memory management
(enif_make_resource_binary)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
While at it, added some types to a record
and did some cleanups suggested by tidier.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
erl_lint has been updated so that it takes the new -export_type()
attribute into account.
This means:
- do not complain about types which are defined but nowhere used in the
module but exported to other modules
- check that all types which are exported are indeed defined in the module
- warn when there are multiple occurrences of exported types.
In doing this change, I've also taken the liberty to introduce many types and
specs for functions of this module and to do small cleanups here and there.
|
|
The Erlang code preprocessor (epp) did not correctly handle premature
end-of-input when defining macros. This bug, introduced in STDLIB 1.16, has
been fixed.
|
|
* origin/pan/otp_8579_autoimport_override:
Update preloaded modules
Update primary bootstrap
Remove outcommented code from erl_lint
Make port_command/3 auto-imported
Remove (harmless) warnings about min/max in core applications
Autoimport min/2 and max/2
Improve coverage of erl_int in testcases
Change warning to error for nowarn_bif_clash compiler directive
Add -compile({no_auto_import,[F/A]}) doc to compiler.xml
Add some testcases to compiler to verify that overriding really happens
Return nowarn_bif_clash functionality but with warning
Teach erl_lint to better override BIFs with local functions and imports
Teach compiler to override autoimport with import
First prototype for local functions overriding autoimported
OTP-8579 Local functions should override auto-imported
Local and imported functions now override the autoimported
BIFs when the names clash. The pre R14 behaviour was that
autoimported BIFs would override local functions. To avoid
that old programs change behaviour, the following will
generate an error:
Doing a call without explicit module name to a local function
having a name clashing with the name of an autoimported BIF
that was present (and autoimported) before OTP R14A
Explicitly importing a function having a name clashing with
the name of an autoimported BIF that was present (and
autoimported) before OTP R14A Using any form of the old
compiler directive nowarn_bif_clash
If the BIF was added or autoimported in OTP R14A or later,
overriding it with an import or a local function will only
result in a warning,
To resolve clashes, you can either use the explicit module
name erlang to call the BIF, or you can remove the autoimport
of that specific BIF by using the new compiler directive
-compile({no_auto_import,[F/A]})., which makes all calls to
the local or imported function without explicit module name
pass without warnings or errors.
The change makes it possible to add autoimported BIFs without
breaking or silently changing old code in the future. However
some current code ingeniously utilizing the old behaviour or
the nowarn_bif_clash compiler directive, might need changing
to be accepted by the compiler.
|
|
* pan/otp_8577_re_pattern_doc:
Add documentation of what part of a re mp() can be used for guard tests
OTP-8577 Document re_pattern properties
Some properties of a compiled re pattern are defined to allow for guard
tests.
|
|
* pan/otp_8611_standard_io:
Teach file:write/read/read_line about named io_servers
OTP-8611 file:write,read and read_line on named io_device()
The file module's functions write,read and read_line now handles named
io_servers like 'standard_io' and 'standard_error' correctly.
|
|
* pan/otp_3626_win_find_executable:
Teach os.erl to find executable names with extension (i.e. .exe) on windows
OTP-3626 os:find_executable bug on Windows
os:find_executable can now be fed with the complete name of the executable
on Windows and still find it. I.e os:find_executable("werl.exe") will work
as os:find_executable("werl").
|
|
certificates.
|
|
|
|
|
|
|
|
|
|
|
