In order to standardize something, you need to establish things thanks to which you are able to express what you want to say.
For example a Notation. The Go Reference manual uses Extended Backus-Naur Form (EBNF) for that and this part is just expressing that. Think of this point not as "Go documentation," but as establishing a "way to communicate". The excerpt you are asking about defines Production's syntax: Production = production_name "=" [ Expression ] "." . and a little further down you have an explanation of what Productions is: Productions are expressions constructed from terms and the following operators, in increasing precedence. So in other words, we are defining here the syntax that will be used later in the documentation, not the specific fields and that is why you can not find "production_name" throughout the rest of the docs. However, for example, hex_digit is a in-docs Production built similarly to what you are looking for: hex_digit = "0" … "9" | "A" … "F" | "a" … "f" . Best Regards, On Fri, 29 Oct 2021 at 12:53, Kamil Ziemian <kziemian...@gmail.com> wrote: > From what I understand about EBNF production_name should be defined using > EBNF notation in manner like below. > > production_name = something1 | something2 > > But I don't see such definition in Spec. > > Best > Kamil > > czwartek, 28 października 2021 o 21:31:07 UTC+2 seank...@gmail.com > napisał(a): > >> There isn't much to it, a "production_name" is just an identifier for the >> set of values defined on the other side of the =, some of which may also be >> identifiers that should be dereferenced/expanded >> >> If it helps, there's a wikipedia entry on it: >> https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form >> >> On Thursday, October 28, 2021 at 7:33:27 PM UTC+2 kziem...@gmail.com >> wrote: >> >>> Hello, >>> >>> From what I understand proper Gopher read at least one time "The Go >>> Programming Language Specification" (https://golang.org/ref/spec) and >>> now I need to read it too. >>> >>> I learn something of Extended Backus-Naur Form to understand it, so if I >>> say something stupid beyond belief, I hope you will forgive me. In the >>> first part "Notation" (https://golang.org/ref/spec#Notation) I believe >>> that I understand meaning of all concepts except of "production_name". On >>> one hand "production_name" means that it is name of the production, not >>> rocket science here. On the other, after reading about EBNF I feel that I >>> should have more information about it. Can you explain it to me? >>> >>> Again I'm new to EBNF, so maybe this is stupid question. >>> >>> Best >>> Kamil >>> >>> -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/02647258-d529-4dac-ac63-8c72874b4a89n%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/02647258-d529-4dac-ac63-8c72874b4a89n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- *Patryk Węgrzynek* Backend Developer Site Reliability Engineer -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAFLRUz5VUT1SW9h9-NSdeUefCj2HF8_FW49L%3Dy7bR7EoY7HY0g%40mail.gmail.com.
