Goland ISO/IEC stantard

[Игорь Авдошкин]

Language Golang Long-Term project? Will he standardized as C/C + +?

[Jan Mercl]

On Tue, Mar 18, 2014 at 9:29 AM, Игорь Авдошкин <avdo...@gmail.com> wrote:
> Language Golang Long-Term project? Will he standardized as C/C + +?

It seems the name of the language ought to be standardized in the first place.

-j

[Gerard]

You mean like Microsoft did with OOXML?

[Gyepi SAM]

A quixotic and apt initial goal for the standards committee!
It should keep them busy for a while and we'll get some work done ;)

-Gyepi

[Konstantin Khomoutov]

On Tue, 18 Mar 2014 01:29:08 -0700 (PDT)
Игорь Авдошкин <avdo...@gmail.com> wrote:

> Language Golang Long-Term project? Will he standardized as C/C + +?

The Go language is officially defined by its Specification, Memory
Model and other documents [1], and has an API stability promise [2] (for
Go 1.x; Go 2.x and later will supposedly have their others similar
promises, of cource).

So...

* It's possible to create an alternative implementation of Go
which will be standards-compliant.
Note that there are already two popular standard implementations:
the one from the original Go authors and another one which is
a GCC backend. Both are FOSS, are developed in the open and are
supported by their open communities.
* No, there's no "comittee standard" approved by some "official body"
such as ANSI, ISO, WTFBBQ or other such entity.
I have no idea though why you would want to have such a standard.
You might want to elaborate on this...

1. http://golang.org/doc/#references
2. http://golang.org/doc/go1compat

[Ian Lance Taylor]

On Tue, Mar 18, 2014 at 1:29 AM, Игорь Авдошкин <avdo...@gmail.com> wrote:
>> Language Golang Long-Term project? Will he standardized as C/C + +?

There are no present plans to pursue a standardization process for Go
through any sort of official standards body. There are no obvious
advantages to pursuing an official standard.

By way of example, Dart, another open source language developed at
Google, is pursuing a language standard via ECMA. In their case, it
is because Dart would ideally be implemented in each browser, which
means several different implementations, some proprietary. Browser
manufacturers have proven reluctant to add a new language without an
existing standard. So for Dart, creating a standard makes sense.

No such reason applies to Go at present.

Ian