|
From: | Germán Arias |
Subject: | Re: Implementation of CFBridgingRelease() on GNUstep |
Date: | Wed, 31 May 2017 19:45:57 -0600 |
Can you point me to where these discussions happened? I'd love to understand in more detail why this is so.-- Daniel
Sent from my iPhone
On Wed, May 31, 2017 at 9:05 PM -0300, "Stefan Bidigaray" <address@hidden> wrote:
Hi Daniel,As everything currently stands, the answer to your question is, yes, CFBridgingRelease is eyewitness to CFRelease. We had a discussion about it either early this morning or last month.That said, since you are the second person to ask about these functions, I believe the safest route is to implement it. I'm going to be out of town until Monday, but I can look at into it then.Based on David's previous comments, I believe the best approach is to make it an alias to objc_release(), if that function exists, and an alias to CFRelease, otherwise. David, can you confirm that is the smartest approach?I apologize for any typos, I'm on my phone.StefanOn May 31, 2017 19:16, "Daniel Ferreira (theiostream)" <address@hidden> wrote:Hi there! I'm Daniel Ferreira, and I'm the student who will be
contributing to GNUstep through Google Summer of Code for the next
three months. I'll be working on getting WebKit to run on top of GS.
That being said, one of the first things I stumbled upon when building
WebKit against GS was the absence of a GS implementation of
CFBridgingRelease
(https://developer.apple.com/reference/foundation/1587932- ).cfbridgingrelease
I asked Ivan about how to deal with this and he was under the
impression that in GNUstep, CFBridgingRelease() should be equivalent
to CFRelease(), but he couldn't state that with absolute certainty.
So this is the question: are they somehow equivalent in CoreBase's
understanding of ARC? And if not, how would you suggest this be
implemented? I didn't see transferring memory ownership to ARC being
dealt with on threads like this[1] about supporting ARC on CoreBase.
Also, only GS thread I could find that addresses the function in
particular is this one[2], and it doesn't look like much help either.
Thanks,
-- Daniel.
[1]: http://lists.gnu.org/archive/html/discuss-gnustep/2015-02/ msg00021.html
[2]: http://lists.gnu.org/archive/html/gnustep-dev/2015-12/ msg00020.html
_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________ Gnustep-dev mailing list address@hidden https://lists.gnu.org/mailman/listinfo/gnustep-dev
[Prev in Thread] | Current Thread | [Next in Thread] |