[erlang-questions] Erlang/OTP 19.0 has been released

[Serge Aleynikov]

The documentation is correct - the option was renamed from 'line_delim' to
'line_delimiter'.

In terms of multi-character line delimiters - the default delimiter is
'\n', but it will correctly handle lines separated by "\r\n" - that was the
unmodified legacy behavior. So it'll correctly parse HTTP headers. What's
changed was the ability to specify an alternative delimiting character,
which is useful for some protocols (e.g. FIX that uses '\1').  The choice
of a single character was for having minimal impact on the existing
implementation.

Note that there is a similar PR for file:read_line/1 (
https://github.com/erlang/otp/pull/757), but it's currently stalled as it
presently only supports reading in raw mode. If there are any volunteers to
help it get working in the non-raw mode, that would help to get it merged
sooner.

On Fri, Jun 24, 2016 at 8:14 AM, Loïc Hoguin <essen@REDACTED> wrote:

> Noticed one small oddity:
>
>   OTP-12837    Application(s): kernel
>
>                Add {line_delim, byte()} option to inet:setopts/2 and
>                decode_packet/3
>
> In the documentation it appears to be {line_delimiter, byte()}.
>
> In the documentation it is listed in the text below the function, but not
> in the types (true for both decode_packet and inet:setopts/gen_tcp:option).
>
> Finally the choice of a single byte is curious. For example in HTTP the
> line delimiter is \r\n.
>
> On 06/22/2016 12:18 PM, Kenneth Lundin wrote:
>
>> Erlang/OTP 19.0 has been released
>> --------------------------------------------------
>>
>> Erlang/OTP 19.0 is a new major release with new features, quite a few
>> (characteristics) improvements, as well as a few incompatibilities.
>>
>> Some highlights of the release are:
>>
>>   * *compiler, stdlib*:
>>       o New preprocessor macros *?FUNCTION_NAME, ?FUNCTION_ARITY*
>>       o New preprocessor directives -error(Term) and -warning(Term) to
>>         cause a compilation error or warning, respectively.
>>
>>   * *gen_statem* a new state machine behavior
>>   * *mnesia_ext*: plugin of external storage solutions to mnesia
>>   * *crypto*: uses EVP interface in OpenSSL resulting in generally
>>     better performance and support for HW acceleration
>>   * *ssh*: performance improvements, uses the new gen_statem behavior
>>   * *ssl*: enhanced error log messages
>>   * *dialyzer*: the support for maps is very much extended both the type
>>     specification syntax and the type analysis.
>>   * *erts*:
>>       o erlang:open_port(spawn, ...) 3-5 times faster
>>       o tracing, extensive improvements (scalability, speed, match
>>         specifications on send/receive, support for lttng, ...)
>>       o dirty schedulers improved
>>       o per process configurable handling of message_queue
>>       o fast loading of multiple modules
>>       o max_heap_size process flag
>>   * *erts/kernel:*
>>       o |Experimental support for Unix Domain Sockets
>>         ||Example: ||gen_udp:open(0, [{ifaddr,{local,"/tmp/socket"}}])|||
>>   * and much more ....
>>
>> You can find the Release Notes with more detailed info at
>>
>> http://www.erlang.org/download/otp_src_19.0.readme
>>
>> You find the source code at github.com <http://github.com/erlang> in the
>> official Erlang repository.
>>
>> Git tag OTP-19.0
>>
>> https://github.com/erlang/otp/tree/OTP-19.0
>>
>> You can also read the documentation on-line here:
>> (see the Release Notes mentioned above for release notes which
>> are not updated in the doc, but the new functionality is)
>>
>> http://www.erlang.org/doc
>>
>> We also want to thank all of you that have contributed with new
>> features, bug-fixes, suggestions and bug reports.
>>
>> The Erlang/OTP Team at Ericsson
>>
>>
>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
> --
> Loïc Hoguin
> http://ninenines.eu
> Author of The Erlanger Playbook,
> A book about software development using Erlang
> _______________________________________________
> 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/20160624/5dce2f88/attachment.htm>