[
https://issues.apache.org/jira/browse/THRIFT-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873824#comment-16873824
]
Kevin Wojniak commented on THRIFT-4895:
---------------------------------------
Cocoa server is working for binary+buffered+ip. Although I had to temporarily
hack the generated output to support exceptions.
{noformat}
$ python3 test/test.py --server cocoa --client c_glib,cpp
Apache Thrift - Integration Test Suite
Wed Jun 26 22:16:37 2019
===============================================================================
server-client: protocol: transport: result:
cocoa-cpp binary buffered-ip success
cocoa-c_glib binary buffered-ip success
===============================================================================
No unexpected failures.
You can browse results at:
file:///Users/kainjow/git/thrift/test/index.html
# If you use Chrome, run:
# cd /Users/kainjow/git/thrift
# python -m http.server 8001
# then browse:
# http://localhost:8001/test/
Full log for each test is here:
test/log/server_client_protocol_transport_client.log
test/log/server_client_protocol_transport_server.log
0 failed of 2 tests in total.
Test execution took 1.9 seconds.
Wed Jun 26 22:16:39 2019
{noformat}
> Revive Cocoa support and add tests
> ----------------------------------
>
> Key: THRIFT-4895
> URL: https://issues.apache.org/jira/browse/THRIFT-4895
> Project: Thrift
> Issue Type: New Feature
> Components: Cocoa - Library, Test Suite
> Reporter: Kevin Wojniak
> Priority: Major
>
> I would like to see the Objective-C (Cocoa) support brought back. The
> suggestion to use Swift is not valid for all use cases for a few reasons:
> # Objective-C is not deprecated and is not going away.
> # Swift has to be written with Objective-C in mind to be backwards
> compatible. This severely limits the ability to use modern Swift. Plus, it
> requires bringing in the Swift runtime (several MB). It is nice to use all
> modern Swift features when using Swift and not have to be reminded of
> Objective-C backwards compatibility.
> # Objective-C library can be used with Swift with no extra cost, but not the
> other way around. Currently 0.12 already has good support by using modern
> Objective-C enums and could be expanded for better Swift support, for example
> adding nullability type annotations.
> # Swift cannot interact with C+++, so if a project is mostly C+++ that must
> interact with Cocoa APIs it must use Objective-C.
> I am working on adding tests for the Cocoa code from the 0.12 version. My
> work in progress is here:
> [https://github.com/kainjow/thrift/commits/kwojniak/cocoa-tests-wip]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
