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

Roger Meier commented on THRIFT-2670:
-------------------------------------

thanks, speed is a good reason for Parcelable!

could you please clean up this:
{noformat}
g++ -DHAVE_CONFIG_H -I. -I../.. -I../../lib/cpp/src/thrift  -I./src  -Wall -g 
-O2 -std=c++11 -MT thrift-t_java_generator.o -MD -MP -MF 
.deps/thrift-t_java_generator.Tpo -c -o thrift-t_java_generator.o `test -f 
'src/generate/t_java_generator.cc' || echo './'`src/generate/t_java_generator.cc
src/generate/t_java_generator.cc: In member function ‘void 
t_java_generator::generate_java_struct_parcelable(std::ofstream&, t_struct*)’:
src/generate/t_java_generator.cc:1588:12: warning: enumeration value 
‘TYPE_VOID’ not handled in switch [-Wswitch]
src/generate/t_java_generator.cc:1681:12: warning: enumeration value 
‘TYPE_VOID’ not handled in switch [-Wswitch]
src/generate/t_java_generator.cc:1537:3: warning: label ‘std’ defined but not 
used [-Wunused-label]
{noformat}

thanks!
;-r

> Android Parcelable Java generation option
> -----------------------------------------
>
>                 Key: THRIFT-2670
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2670
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Java - Compiler
>            Reporter: Marek Kedzierski
>              Labels: Android
>             Fix For: 1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I added a java compiler option, for Android, to generate parcelable 
> structures.  This means they implement android.os.Parcelable interface, and 
> also define an inner static member called CREATOR.  All data types are 
> supported except for Sets, because android parcel doesn't have a way to 
> write/read sets.  
> I am making a github pull request for this.   
> https://github.com/apache/thrift/pull/196



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to