|| at Jan 30, 2013 at 5:40 pm
On Thu, Jan 31, 2013 at 1:26 AM, Dawid Polak wrote:
This is not a problem of Go itself, as Windows cmd doesn't expand the
I know. But documentation should mention more abut this limitation.
set up GOPATH and use go build/install?
Of course - i have - but many times go run is used for test run only, and
simple - is faster.
it is only faster if you only run the same set of program once.
probably you can create a script (or better, a Go program) to wrap the go
expand wildcards in the argument (use path/filepath.Glob and os/exec for
we don't require alternative console on windows.
But maybe documentation should suggest this solution, or in 'go run'
implement alternative command line parameter format - for example " go run
' *.go ' "
"go run" is only supposed to run single file commands for test purpose, so
don't support read the source code from stdin, because the authors' fear
will abuse that (however, as i frequently run sample programs from
i do have a script for that).
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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.