My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 409: protocol message fields with Java reserved words not always compiled correctly
3 people starred this issue and may be notified of changes. Back to list
Status:  New

Sign in to add a comment
Reported by, Aug 13, 2012
What steps will reproduce the problem?
1. create a protocol message definition with a "class" field
2. generate Java code for this message
3. observe errors in generated source

What is the expected output? What do you see instead?

Java code that compiles.  Instead, methods such as "int getClass()" produce compiler errors.

What version of the product are you using? On what operating system?

libprotoc 2.4.1, on RHEL 5.8

Please provide any additional information below.

It would appear some thought has gone into this, for example, the C++ code has methods named "class_()", "has_class_()", etc.  Otherwise, this should be considered a low-priority enhancement at best.

Feb 1, 2013
Project Member #1
(No comment was entered for this change.)
Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low
Sign in to add a comment

Powered by Google Project Hosting