You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King III (JIRA)" <ji...@apache.org> on 2019/01/14 15:04:04 UTC

[jira] [Resolved] (THRIFT-2885) Support fullcamel in cocoa compiler

     [ https://issues.apache.org/jira/browse/THRIFT-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King III resolved THRIFT-2885.
---------------------------------------
       Resolution: Won't Do
         Assignee: James E. King III
    Fix Version/s: 1.0

As support for the older cocoa compiler and library have been removed (see THRIFT-4719), all of the issues in Jira related to that code have also been removed.  For legacy cocoa support you can use version 0.12.0 - everyone is expected to move to swift if they want to use the next release of Thrift.

> Support fullcamel in cocoa compiler
> -----------------------------------
>
>                 Key: THRIFT-2885
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2885
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Cocoa - Compiler
>    Affects Versions: 0.9.2
>            Reporter: Todd Gardner
>            Assignee: James E. King III
>            Priority: Minor
>             Fix For: 1.0
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Obj-c tends to follow camelcase for variables and method names, and while we could use camelcase in the IDL to get that, we use languages that have snake case variable names; so it seems like the options are to do add compiler option to do the former or the latter transformation.
> Given java has fullcamel, it seems like the path of least resistance is to write the variables in snake_case in the idl and add compiler support for camelcase to certain languages; this is a proposal to do that for obj-c.
> I intend to take a stab at this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)