For R2 I would go 64bit only. Make the R1 ABI stable on x86-64, and have
R2 include a compatibility with that. This way, people can continue to
use R1 apps with R2 (but they can't use BeOS R5 apps anymore).
I think having each release compatible with release N-1 is good enough,
especially as we don't release very often. Of course, if someone plans
to maintain gcc2 compatibility in the R2 branch, why not. But that won't be
me.
Adrien.
On Thu, Dec 01, 2016 at 10:38:15PM +0100, Ralf Schülke wrote:
Why not drop gcc2 and BeOS r5 compatibility, de need more user and
developer and de can this do, lets do. All arguments with gcc2 are out of
time.
No one is forcing you to use it. I plan to spend my time maintaining it
and you can't prevent me from doing that. For now there are some gcc2
only, closed source apps, that I still want to use. I hope I can someday
replace them, but so far it is not completely the case.
