[erlang-questions] OTP R16B01 has been released

Tom Burdick thomas.burdick@REDACTED
Thu Jun 20 16:51:12 CEST 2013

I like the idea given above of having an intelligent start function. It
obviously already knows which applications need to be started, why bother
telling me instead of just starting them?

If the current behaviour is required application:start_all(myapp) would be
cool. It'd save me some hassles.


On Thu, Jun 20, 2013 at 6:32 AM, Kenneth Lundin <kenneth.lundin@REDACTED>wrote:

> The requirement of asn.1 from public_key was introduced already in R16B
> but without that beeing reflected in the app file.
> We had several reports from people having trouble with for example SSL in
> R16B because asn.1 was missing in their system and the error indication was
> not obvious.
> Now it is unfortunate that application start complains about asn.1 not
> beeing started when asn1 not needs to be started since it is only a library
> , it does not start any processes. The same goes for public_key it does not
> start any processes and there is no need to start it.
> The distinction between library applications and "living" applications
> should be addressed in the application module.
> /Kenneth , Erlang/OTP Ericsson
> Den 20 jun 2013 02:37 skrev "Tom Burdick" <thomas.burdick@REDACTED>:
> I noticed today after updating that public_key now requires asn1, what
>> gives?
>> Eshell V5.10.2  (abort with ^G)
>> 1> application:start(public_key).
>> {error,{not_started,asn1}}
>> Tom
>> On Wed, Jun 19, 2013 at 8:26 AM, Kenneth Lundin <kenneth.lundin@REDACTED
>> > wrote:
>>> Erlang/OTP R16B01 has been released.
>>> OTP R16B01 is a service release with mostly a number of small
>>> corrections and user contributions. But there are some new functions worth
>>> mentioning as well, here are some of them:
>>>    - Migration of memory carriers between allocator instances, when
>>>    enabled it will result in reduced memory footprint when the memory load is
>>>    unevenly distributed between scheduler specific allocator instances.
>>>    - Interruptible term_to_binary, (thanks to Erik Stenman)
>>>    - Added the +sfwi <interval> Scheduler Forced Wakeup Interval
>>>    - All crypto functions except the block chipers will now chunk large
>>>    input into several calls to avoid blocking the scheduler for too long.
>>>    - Elliptic curve support in crypto, ssl and ssh(thanks to Andreas
>>>    Schultz)
>>>    - Lift static limitation (FD_SETSIZE) for file descriptors on Mac OS
>>>    X. (thanks to Anthony Ramine)
>>>    - Removed a lock around GC statistics counter
>>>    - Many small improvements and in Diameter
>>>    - 60 user contributions
>>>     You can find the README file with more detailed info at
>>> http://www.erlang.org/download/otp_src_R16B01.readme
>>> You can download the full source distribution from
>>> http://www.erlang.org/download/otp_src_R16B01.tar.gz
>>> http://www.erlang.org/download/otp_src_R16B01.readme (this file)
>>> Note: To unpack the TAR archive you need a GNU TAR compatible program.
>>> For installation instructions please read the README that is part of
>>> the distribution.
>>> You can also find this release at the official Erlang/OTP
>>> Git-repository at Github here:
>>> https://github.com/erlang/otp tagged *OTP_R16B01*
>>> The Windows binary distribution can be downloaded from
>>> http://www.erlang.org/download/otp_win32_R16B01.exe
>>> http://www.erlang.org/download/otp_win64_R16B01.exe
>>> On-line documentation can be found at http://www.erlang.org/doc/.
>>> You can also download the complete HTML documentation or the Unix manual
>>> files
>>> http://www.erlang.org/download/otp_doc_html_R16B01.tar.gz
>>> http://www.erlang.org/download/otp_doc_man_R16B01.tar.gz
>>> We also want to thank those that sent us patches, suggestions and bug
>>> reports,
>>> The Erlang/OTP Team at Ericsson
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130620/f9cc1530/attachment.htm>

More information about the erlang-questions mailing list