discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should we split the project into two branches?


From: Frederik Seiffert
Subject: Re: Should we split the project into two branches?
Date: Mon, 14 Feb 2022 20:34:09 +0100

Sorry I just realized I misread "ancient version of the language" for "using GCC". It still doesn’t seem like a big deal to me wrt. contributing, but then again my changes were usually pretty contained.


Am 14.02.2022 um 20:30 schrieb Frederik Seiffert <frederik@algoriddim.com>:



Am 14.02.2022 um 18:39 schrieb Andreas Fink <afink@list.fink.org>:

It does the project a huge reality check to tell developers they 'have to use an ancient version of the language *IF THEY WANT TO CONTRIBUTE TO GNUSTEP*'.

Why do you think that’s the case? I’ve contributed many changes over the last years and haven’t once built GNUstep with GCC. I just open a pull request with my changes on GitHub, and rely on the CI to automatically build and test the changes for me with both compilers and across different platforms. If something should fail I get an email and can force push any fixes needed before they would get merged, although that’s rarely the case because for most kinds of changes it won’t matter which compiler is used.

I’d never write any new *app* code without ARC, and would definitely recommend converting any existing apps if you can control the environment where they are built, but IMO it’s fine that the GNUstep libraries don’t use it – it definitely doesn’t keep me from contributing. Most of the code works and is well tested over the years/decades, and so I’m not sure what exactly would be gained by a conversion in comparison to the downside of loosing GCC users.

Frederik



reply via email to

[Prev in Thread] Current Thread [Next in Thread]