<pre><code>package main
import (
"fmt"
)
var name string = "Josh"
func main() {
var name string = "Ben"
fmt.Println(name) // Ben
// PROBLEM: How to print variable that Josh inside?
}
</code></pre>
<hr/>**评论：**<br/><br/>lapingvino: <pre><p>the {} introduces a new scope, and the name in the main function shadows the outside name. What you should do here instead is consciously avoid using the same name. Also, you could create a top level struct called e.g. "global" that has a field "name". You can really do that however you want, but keep in mind that avoiding globals can spare you a lot of problems ;).</p></pre>mc_hammerd: <pre><p>yea. one alternative is a 'trick' c programmers use sometimes. put everything global in a global struct. ex: <a href="http://play.golang.org/p/3JyD_cXvxe" rel="nofollow">http://play.golang.org/p/3JyD_cXvxe</a></p></pre>nicerobot: <pre><pre><code>package main
import "fmt"
var name = "Josh"
func main() {
globalname, name := name, "Ben"
fmt.Println("Hello ",name,"and",globalname)
}
</code></pre>
<p>The point here is that you recognize you are explicitly changing the <code>name</code> variable to a different scope yet still intend to use the global <code>name</code> too.</p></pre>dazzford: <pre><p>Others have given you workarounds but the real solution is to not use global variables. </p>
<p>They are an anti-pattern and a code smell.</p></pre>
