You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2009/11/20 03:16:39 UTC

[jira] Commented: (AVRO-221) Mangle conflicting names in generated code for Java

    [ https://issues.apache.org/jira/browse/AVRO-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780378#action_12780378 ] 

Philip Zeyliger commented on AVRO-221:
--------------------------------------

>From the -dev list:

{quote}
Philip Zeyliger wrote:

    I think that for keywords, that language's implementation should
    generate something sensible if there's code generation installed.  So,
    the Java specific compiler could have a list of Java keywords
    embedded.  If it sees "long", it just replaces it with "long_" in the
    generated code.  The only reserved words in Avro are the names of
    built-in avro types...

    Would that be sensible?


+1 I agree that we should only mangle names when they conflict.

Doug
{quote}

> Mangle conflicting names in generated code for Java
> ---------------------------------------------------
>
>                 Key: AVRO-221
>                 URL: https://issues.apache.org/jira/browse/AVRO-221
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Philip Zeyliger
>            Assignee: Philip Zeyliger
>
> Generated Java code should support fields that conflict with Java reserved words.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.