| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They are broken and hard to make work.
They have never worked: if you import "/tmp/x"
from "/home/rsc/p.c" then the compiler rewrites
this into import "/home/rsc/tmp/x", which is
clearly wrong.
Also we just disallowed the : character in import
paths, so import "c:/foo" is already not allowed.
Finally, in order to support absolute paths well in
a build tool we'd have to provide a mechanism to
instruct the compiler to resolve absolute imports
by looking in some other tree (where the binaries live)
and provide a mapping from absolute path to location
in that tree. This CL avoids adding that complexity.
This is not part of the language spec (and should not be),
so no spec change is needed.
If we need to make them work later, we can.
R=ken2
CC=golang-dev
http://codereview.appspot.com/5712043
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also allow multiple invalid import statements in a
single file.
Fixes issue 3021. The changes to go/parser and the
language specifcation have already been committed.
R=rsc, gri
CC=golang-dev
http://codereview.appspot.com/5672084
Committer: Russ Cox <rsc@golang.org>
|
| |
|
|
|
|
| |
R=golang-dev, gri
CC=golang-dev
http://codereview.appspot.com/5674112
|
| |
|
|
|
|
|
|
|
|
|
| |
X ,s;^// \$G (\$D/)?\$F\.go *$;// compile;g
X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A *$;// build;g
X ,s;^// \$G (\$D/)?\$F\.go && \$L \$F\.\$A && \./\$A\.out *$;// run;g
X ,s;^// errchk \$G( -e)? (\$D/)?\$F\.go *$;// errorcheck;g
R=golang-dev, bradfitz
CC=golang-dev
http://codereview.appspot.com/5673079
|
|
|
R=ken2
CC=golang-dev
http://codereview.appspot.com/5609044
|
