Just curious, but... how is this 'new terminology'?

I kind of (from a C background, so forgive this naive assumption) assumed
that by exported/unexported Go was literally going the same thing as C / C++

ie. Each package is a library with an exposed ABI that only contains the
symbols that have capital letters in them. The rest are internal symbols
that do not appear in the ABI.

How is this different in Go?

...because if it *is* different then the terminology *is* confusing. :(

On Saturday, March 23, 2013 5:22:09 AM UTC+8, Andrew Gerrand wrote:

On 22 March 2013 12:52, Nate Finch <nate....@gmail.com <javascript:>>wrote:
It's not a big deal, and maybe it's good to prevent people from assuming
they know what private vs public means in Go, and ending up being somewhat
wrong, as opposed to not assuming they know what exported/unexported mean,
and forcing them to look it up.

It is good to use new terminology for new concepts. I think the naming
works well here.

As a data point, I've explained this concept probably hundreds of times
and people seem to catch on pretty quickly.

It seems that programmers are good at associating names with concepts. :-)

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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 15 of 16 | next ›
Discussion Overview
groupgolang-nuts @
postedMar 22, '13 at 7:14p
activeMar 23, '13 at 4:28a



site design / logo © 2021 Grokbase