Go get ellipsis (#1)

* gi: rename gi_c into _gi_c

* gi: rename test into _test

* gi: fix README syntax

.gitignore

@@ -3,12 +3,12 @@
 *.dot
 cmd/goexports/goexports
 gi
-gi_c/*.o
-gi_c/gi
-gi_c/loop2
-gi_c/l2
-gi_c/deps/lightning-*
-gi_c/deps/lib
-gi_c/deps/include
-gi_c/deps/share
-gi_c/deps/*.gz
+_gi_c/*.o
+_gi_c/gi
+_gi_c/loop2
+_gi_c/l2
+_gi_c/deps/lightning-*
+_gi_c/deps/lib
+_gi_c/deps/include
+_gi_c/deps/share
+_gi_c/deps/*.gz

README.md

@@ -6,7 +6,7 @@ A Go interpreter in go
 
 Tests are simple standalone go programs to be run by `gi` executable.
 Scripts are converted to go test examples for execution by `go test` as well.
-To create a new test, simply add a new .gi file, specifying expected output at end of program in a `// Output:' comment block like in the following example:
+To create a new test, simply add a new .gi file, specifying expected output at end of program in a `// Output:` comment block like in the following example:
 
 ```go
 package main
@@ -18,7 +18,7 @@ func main() {
 // Hello
 ```
 
-Then in `test/`, run `make` to re-generate `interp/eval_test.go`
+Then in `_test/`, run `make` to re-generate `interp/eval_test.go`
 
 When developping/debugging, I'm running `gi` on a single script, using `-a` and `-c` options to display AST and CFG graphs, and instrumenting code with temporary println statements to diagnose problems.
 

_test/gen_example.sh

@@ -2,7 +2,7 @@
 
 echo 'package interp'
 echo
-echo '// Do not edit! File generated by ../test/gen_example.sh'
+echo '// Do not edit! File generated by ../_test/gen_example.sh'
 echo
 echo 'import "github.com/containous/gi/export"'
 echo