> No. The next number is for the next release, and ideally, we want to sit on
> it for another 10 years or so. We offer no compatibility before the RM says,
> done with the release. Up until then, you can twiddle, after that, no more
> changes to the abi, though, you can bug fix it.
Sounds
On Jun 8, 2011, at 1:25 AM, Nicola Pero wrote:
> But - you're right that we should bump it, so I bumped it :-)
> I suppose we could bump it again when we get into phase 3, when we're finished
> with the changes.
No. The next number is for the next release, and ideally, we want to sit on it
for a
On Wed, Jun 08, 2011 at 09:25:09AM +0100, Nicola Pero wrote:
> >>> This patch completes the removal of the public part of the
> >>> Traditional Objective-C runtime API from libobjc.
> >>>
> >>> From now on, the only supported API is the "Modern" API. :-)
> >>
> >> If you are removing exported fu
I also bumped the API version #define marker.
Committed to trunk.
Thanks
Index: ChangeLog
===
--- ChangeLog (revision 174798)
+++ ChangeLog (working copy)
@@ -1,5 +1,9 @@
2011-06-08 Nicola Pero
+ * objc/objc.h (__GNU
>>> This patch completes the removal of the public part of the
>>> Traditional Objective-C runtime API from libobjc.
>>>
>>> From now on, the only supported API is the "Modern" API. :-)
>>
>> If you are removing exported functions from libobjc.so, you should
>> bump VERSION= in libobjc/configure
>> This patch completes the removal of the public part of the
>> Traditional Objective-C runtime API from libobjc.
>>
>> From now on, the only supported API is the "Modern" API. :-)
>
> If you are removing exported functions from libobjc.so, you should
> bump VERSION= in libobjc/configure.ac.
On Tue, Jun 07, 2011 at 09:37:42PM +0200, Nicola Pero wrote:
> This patch completes the removal of the public part of the
> Traditional Objective-C runtime API from libobjc.
>
> From now on, the only supported API is the "Modern" API. :-)
If you are removing exported functions from libobjc.so, y
