Issue 246 in protobuf-dt: Aggregate syntax for custom options should support semicolon as a separator

3 views
Skip to first unread message

proto...@googlecode.com

unread,
Jan 30, 2014, 10:55:31 AM1/30/14
to proto...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 246 by nicolas....@gmail.com: Aggregate syntax for custom options
should support semicolon as a separator
http://code.google.com/p/protobuf-dt/issues/detail?id=246

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


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages