[ 
https://issues.apache.org/jira/browse/THRIFT-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194433#comment-13194433
 ] 

Hudson commented on THRIFT-1504:
--------------------------------

Integrated in Thrift #396 (See [https://builds.apache.org/job/Thrift/396/])
    THRIFT-1504: Cocoa Generator should use local file imports for base Thrift 
headers
Client: cocoa
Patch: Steve White

Updates thrift headers as global imports instead of local imports

jfarrell : http://svn.apache.org/viewvc/?view=rev&rev=1236503
Files : 
* /thrift/trunk/compiler/cpp/src/generate/t_cocoa_generator.cc

                
> Cocoa Generator should use local file imports for base Thrift headers
> ---------------------------------------------------------------------
>
>                 Key: THRIFT-1504
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1504
>             Project: Thrift
>          Issue Type: Bug
>          Components: Cocoa - Compiler
>    Affects Versions: 0.8
>            Reporter: Steve White
>            Assignee: Steve White
>            Priority: Minor
>              Labels: patch
>             Fix For: 0.9
>
>         Attachments: THRIFT-1504.patch
>
>
> The Cocoa generator imports various thrift files as global imports instead of 
> local importss.  This ends up requiring that the user alter their header 
> search paths to include the directories the generated thrift code is in, or 
> the user has to edit the generated files to remove this.
> e.g.
> #import <TProtocol.h>
> #import <TApplicationException.h>
> #import <TProtocolUtil.h>
> #import <TProcessor.h>
> vs.
> #import "TProtocol.h"
> #import "TApplicationException.h"
> #import "TProtocolUtil.h"
> #import "TProcessor.h"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to