Hi Tom, thanks for your reply.
I hope that at some point you'll revisit your stance on ARC... it's the way forward from Apple's perspective, and they have it enabled on all new projects by default; there are good reasons to use it. Of course, you're not bound by their design philosophy, but there will probably come a point where ARC is mandatory under XCode, at which point the Adobe SDK may not be usable anymore. Anyway, that's all conjecture, no point in grinding on it now.
Converting the SDK to ARC is not as simple as just removing the retain and releases, although of course that's part of it. I did a few hours of that and it eliminated one category of errors, but there were many more that were a lot more difficult. Part of the issue is that you're using some open-source code (I believe) that was written in 2009 or earlier, and all of THAT needs to be corrected as well, and some of the socket/network and security code - like Peter Bakhyryev's NetConnection.m/.h in psconnection/networking, is especially complex. I tried to find some updated examples of that code that would work in the project, but it seems like some of it changed in ways that may not work well with the original SDK. (I admit I'm a little out of my depth at the sockets level.)
Bridged casting is needed for Core Foundation code, as in:
CFStreamCreatePairWithSocketToHost(kCFAllocatorDefault, (__bridge CFStringRef)(myServerName), 49494, &readStream, &writeStream);
inputStream = (__bridge NSInputStream *) readStream;
outputStream = (__bridge NSOutputStream *) writeStream;
To be honest, I had never heard of bridged casting until I had to get this code to compile and had to learn enough to get it going. It's related to memory management and I had to make a guess that this was the correct variant. I did manage to get enough code going to allow a connection to PS to happen and to successfully transmit some simple commands, by removing release/retain and using this bridged casting mode when needed, but it's probably a fairly small subset of the overall kit's potential functionality. Maybe it'll be enough for what I need right at the moment, but I guess we'll have to see how it works going forward.
Here's a stackoverflow thread with a bridged casting issue:
http://stackoverflow.com/questions/6725558/cast-of-objective-c-pointer-type-nsstring-to-c-pointer-ty...
To be clearer, the problematic issues are related to ARC and probably not iOS5 specifically. But trying to integrate the whole networking library (as the documentation for the kit instructs) into an existing project that had ARC on was a real nightmare. I even tried disabling ARC on the networking library files individually with the -fno-obj-arc, but that didn't solve the problem, some ARC issues persisted and I didn't know how to solve them. 😕
(As an aside, can you feed the Forum Gods and undo my idiotic "msubzbbvsj" screen name? Either clear it, or set it to "slinberg" or "Steve Linberg" or something sensible like that? I didn't realize I was creating anything when I accidentally typed that, and it looks like I can't change it myself.)
4
Replies
AdChoices