search

blueszhangsh / protobuf-dt

Automatically exported from code.google.com/p/protobuf-dt
0 stars 0 forks source link

Aggregate syntax for custom options should support semicolon as a separator #246

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The line:

option ( common.commandOptions ) = { commandWireId : 1; commandClassUuid : 
"..." };

Should be syntactically valid. Instead, the editor shows error markers:

  Multiple markers at this line
  - missing '}' at ';'
  - mismatched input 'commandClassUuid' expecting '}'

Workaround:

Replace semicolon with colon or space.

com.google.eclipse.protobuf 1.4.3.2013071513
protobuf 2.4.1

Original issue reported on code.google.com by nicolas....@gmail.com on 30 Jan 2014 at 3:55