Well, getting MRC right is just a matter of debugging... Maybe it could be
possible to write an ObjC 2.0 -> 1.0 preprocessor doing the tedious job. Then
you could even use gcc for ObjC 2.0.
But generally you are right. If majority thinks ObjC 2.0 is beneficial and
clang is the way to go, it is
its not only about converting your code. There is a gazillion of libraries
which users use which had been developed by others. Converting everything
backwards is a drawback.
Think of if you try to convert the linux kernel back to K C. Its doable but
its a very bad idea.
My main app originally
> Am 20.11.2023 um 16:10 schrieb Andreas Fink :
>
> Without support for ARC, the vast majority of code written in the past 15
> years will not work (or eat memory without ever freeing it up). Apple's
> reference guide to Objective C 2.0 which introduces ARC is from 2008!
Well, if you know
On 20 Nov 2023, at 15:39, Riccardo Mottola wrote:
>
> Hi,
>
> Andreas Fink wrote:
>> As far as renaming goes, well the packages in debian are so far outdated and
>> seem no longer maintained that we should try to get a newer version into
>> debian at some point. But im not sure on how that
Hi,
Andreas Fink wrote:
As far as renaming goes, well the packages in debian are so far
outdated and seem no longer maintained that we should try to get a
newer version into debian at some point. But im not sure on how that
process works . It might fail due to non support of gcc and maybe
