Comment #10 on issue 247 by [email protected]: Ability to redirect file output to stdout
http://code.google.com/p/protobuf/issues/detail?id=247
The C++ parser and descriptor validation code is a lot more complicated than you might imagine. The most difficult part is custom options: a custom option can be used in the same file where it is defined -- even before or *inside of* its own definition.
So, porting would be difficult, and likely buggy. Moreover, keeping the code in sync with the C++ parser would be annoying.
On the other hand, it would be very easy to write a comprehensive test -- just parse all the unit test .proto files using both the C++ and Java parsers and verify that identical DescriptorProtos come out.
After years of arguing against a Java port of the parser, I am starting to think that it may be time to give in... Even inside Google we have a hard time stopping Java users from writing their own .proto parsers (which are almost always broken).
-- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
