Defining public and private
Many modern languages provide a set of options when declaring constants/variables/functions/methods that detail when a method can be called.
Go simplifies these visibility choices down to two types:
- Public (exported)
- Private (not exported)
Public types are types that can be referred to outside of the package. Private types can only be referred to inside the package. To be public, the constant/variable/function/method must simply start with an uppercase letter. If it starts with a lowercase letter, it is private.
There is a third type of visibility that we don't cover here: internally exported. This occurs when a type is public but in a package, located within a directory called internal/
. Those packages can only be used by packages within a parent directory. You can read about this here: https://golang.org/doc/go1.4#internalpackages.
Let's declare a package and create some public and private methods:
package say import "fmt" func PrintHello() { fmt.Println("Hello") } func printWorld() { fmt.Println("World") } func PrintHelloWorld() { PrintHello() printWorld() }
We have three function calls, two public (PrintHello()
and PrintHelloWorld()
) and one private (printWorld()
). Now, let's create package main
, import the say
package, and call our functions:
package main import "github.com/repo/examples/say" func main() { say.PrintHello() say.PrintHelloWorld() }
Now, let's compile and run it:
$ go run main.go Hello Hello World
These work because PrintHello()
and PrintHelloWorld()
are both exported (public) functions. PrintHelloWorld()
calls the private printWorld()
, but that is legal because they are in the same package.
If we try to add say.printWorld()
to func main()
and run it, we will get the following:
./main.go:8:2: cannot refer to unexported name say.printWorld
Public and private apply to variables declared outside functions/methods and type declarations.
By the end of this short and sweet section, you've acquired the knowledge of Go's public and private types. This will be useful in code where you do not want to expose types in your public API. Next, we will look at arrays and slices.