qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-22 02:34:40 -07:00
Code Releases Activity
26fd5252f4
go/test/syntax
History
Ian Lance Taylor c30b570468 test: Match gccgo error messages. 
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
2010-09-09 22:40:25 -07:00
..
forvar.go
import.go gc: tweak error messages, avoid internalization settings in bison 2010-01-28 15:57:44 -08:00
interface.go
semi1.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
semi2.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
semi3.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
semi4.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
semi5.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
semi6.go gc: tweak error messages, avoid internalization settings in bison 2010-01-28 15:57:44 -08:00
semi7.go Match gccgo error messages. 2010-02-04 21:31:30 -08:00
topexpr.go test: Match gccgo error messages. 2010-09-09 22:40:25 -07:00
vareq1.go gc: more accurate error description 2010-05-24 17:07:51 -07:00
vareq.go gc: more accurate error description 2010-05-24 17:07:51 -07:00