erlang / eep Goto Github PK

I was reading https://www.erlang.org/eeps/eep-0060 and iee754float there looks like a typo to me.

Seems to be a mistake in the documentation for EEP0047.

https://www.erlang.org/eeps/eep-0047.html#backwards-compatibility

It says 42, but this was removed in 24.

This is more of a question/request for guidance that an issue.

EEP-55's Backwards Compatibility seems to refer to using old code on an Erlang/OTP version that already supports the pinning operator (e.g. OTP 24, 25, ...).

I'm wondering how we'd be able to use new code that uses it in older Erlang/OTP-supported software (e.g. OTP 19, 20, ...). Would a parse transform of any kind be possible, here?

Thanks.

The following EEPs are outdated:

• EEP 48: Documentation storage and format: it's in draft and standards track, but the docs says EDoc implements EEP-48;
• EEP 58: Map Comprehension: stills on the standards track but the feature is in OTP 26;
• EEP 61: Built-in dynamic type: same as EEP 58.

If you go here:

https://github.com/erlang/otp/releases

You see EXE installer for Windows. This contrasts with other programming
languages that offer both an executable installer and ZIP files that can be
extracted and run. For example Go:

https://golang.org/dl

and Nim:

https://nim-lang.org/install_windows.html

Python:

https://python.org/downloads/release/python-373

and C#:

https://dotnet.microsoft.com/download/dotnet-core/2.2

PHP:

https://windows.php.net/download

Perl:

http://strawberryperl.com/releases.html

DISCLAIMER

I am not a lawyer and all I have written there is about my limited knowledge and what I have found on the internet. It will require some professional lawyer insights.

Right now we are using copyright footer in form of:

Copyright
=========

This document has been placed in the public domain.

However "public domain" isn't something that exists in many jurisdictions (on CC mailing list there is information that it didn't existed in Sweden in 2007), and other jurisdictions do not allow to voluntary give up your copyright to the PD. This mean that this clause can be void sometimes, and that can be a threat to the Erlang community. I think that we should contact some lawyers that specialise in copyrights and validate whether we can and should use such disclaimer or maybe we should require some more detailed licensing there (like CC0 or BSD-0).