In day 2 of the go tutorial there is this exercise:
Why may it be useful to have a private type with exported fields?
For example:
package geometry
type point struct {
X, Y int;
name string;
}
Notice that point
is lowercase and thus not exported, whereas the fields X and Y are uppercase and thus are. It seems to me, that in order to have access to one of the exported fields, you would have to be able to write something like.
p.X
But in order for that to be possible, p would have to have a declaration like such:
var p geomitry.point;
or
p := new(geomitry.point);
This however is not possible (afaik), since the type declaration for point isn't exported.
But you could have a public constructor, right?
So if you had a NewGeometryPoint
func defined, then you maybe could do (haven't tested against the compiler)
p := NewGeometryPoint(640,480);
fmt.Println("X:",p.X, "Y:",p.Y);
An abstract base type ?
package geometry
type point struct {
X, Y int;
}
type Point struct {
point;
name string;
}
type Rect struct {
P1, P2 point;
name string;
}
When using the JSON package (http://golang.org/pkg/json/). You need to have exported fields, to pass a type to json.Marshal(), but you might not want to have that type publicly available to other external packages.