qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-24 23:57:57 -07:00
Code Releases Activity

test: Match gccgo error messages.

Browse Source 
With the recursive descent parser that gccgo uses, I think
that it doesn't make sense to try to match a statement where a
statement is not expected.  If the construct is not a
statement, you will just get bizarre error messages.

topexpr.go:9:1: error: expected declaration
topexpr.go:14:1: error: expected declaration
topexpr.go:19:1: error: expected declaration

R=rsc, r2
CC=golang-dev
https://golang.org/cl/2175041
This commit is contained in:
Ian Lance Taylor 2010-09-09 22:40:25 -07:00
parent f5089ffff4
commit c30b570468
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
test/syntax/topexpr.go
View File

@ -6,15 +6,15 @@
package main
fmt.Printf("hello") // ERROR "non-declaration statement outside function body"
fmt.Printf("hello") // ERROR "non-declaration statement outside function body|expected declaration"
func main() {
}
x++ // ERROR "non-declaration statement outside function body"
x++ // ERROR "non-declaration statement outside function body|expected declaration"
func init() {
}
x,y := 1, 2 // ERROR "non-declaration statement outside function body"
x,y := 1, 2 // ERROR "non-declaration statement outside function body|expected declaration"