From 31c99ff93b2271d2546434fed0eb0f715f3bd783 Mon Sep 17 00:00:00 2001 From: Leandro Moreira Date: Thu, 4 May 2017 11:02:53 -0300 Subject: [PATCH] removes extra [ char --- en/01.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/01.3.md b/en/01.3.md index 1d4be8bf..8a952019 100644 --- a/en/01.3.md +++ b/en/01.3.md @@ -19,7 +19,7 @@ This command is for compiling tests. It will compile packages and dependencies i - If there are many files in the folder, but you just want to compile one of them, you should append the file name after `go build`. For example, `go build a.go`. `go build` will compile all the files in the folder. - You can also assign the name of the file that will be generated. For instance, in the `mathapp` project (in section 1.2), using `go build -o astaxie.exe` will generate `astaxie.exe` instead of `mathapp.exe`. The default name is your folder name (non-main package) or the first source file name (main package). -(According to [The Go Programming Language Specification](https://golang.org/ref/spec), package names should be the name after the word `package` in the first line of your source files. It doesn't have to be the same as the folder name, and the executable file name will be your folder name by default.]) +(According to [The Go Programming Language Specification](https://golang.org/ref/spec), package names should be the name after the word `package` in the first line of your source files. It doesn't have to be the same as the folder name, and the executable file name will be your folder name by default.) - `go build` ignores files whose names start with `_` or `.`. - If you want to have different source files for every operating system, you can name files with the system name as a suffix. Suppose there are some source files for loading arrays. They could be named as follows: