Bringing back ObjC would be great. We could generate several bug fixes to
keep it going a few more years. Is there more documentation about the test
infrastructure? I didn't see much more than the read me, but I could dig
into it more.
Kevin
On Mon, Apr 22, 2019 at 10:01 AM James E. King III wr
Releases for this project are very expensive. We have about 28
languages to support. It would make more sense to reinstate the objc
code for the next major release if people are still using it and the
premise that everybody is moving to Swift was in fact unfounded. In a
project this complex, rem
Instead of bringing back the objc code and fully supporting it going
forward, what about releasing one or more 0.12 minor updates to fix a few
bugs in the objc code? I can make issues and PRs for the changes.
Kevin
On Mon, Apr 22, 2019 at 5:51 AM James E. King III wrote:
> There should be no in
There should be no incompatibilities if both sides are using binary
protocol, for example, since that format has been very stable.
We haven't expressly done cross-version testing in our CI however the
compatibility should work.
We also need someone to write the TestClient and TestServer for swift
Hi Jim,
Sorry for the delay in responding. Other tasks have taken priority!
Cocoa is Apple specific, but there is GNUstep, however that is not widely
used. I do notice the existing Swift port is still using the Cocoa
libraries, and seems to be a direct, although incomplete, port from the
Objectiv
Hi,
The consensus was that cocoa has been deprecated since 2012, nobody was actively
pushing it forward, it was never integrated into the cross-language
integration test suite,
and the project has support for 28 languages and limited resources to
do that. Given the
long deprecation time and vario
In general doesn't objective-c have a wider scope then swift anyway. Like
swift is targeted for mac but you can compile objective-c with gcc on any
nix?
On Friday, March 22, 2019, Steve Yegge wrote:
> I'd like to second this. I have a large Objective-C app that won't be
> ported to Swift in the
I'd like to second this. I have a large Objective-C app that won't be
ported to Swift in the next few years.
On Fri, Mar 22, 2019 at 1:54 PM Kevin Wojniak
wrote:
> Hi,
>
> I am curious as to why the Objective-C implementation was removed, since
> Objective-C is not a deprecated language. The d
Hi,
I am curious as to why the Objective-C implementation was removed, since
Objective-C is not a deprecated language. The documentation says to use
Swift. However, Swift is not fully backwards compatible with Objective-C.
Also, bringing in Swift to Objective-C means bringing in the entire Swift
r
