Ola Söder

@obarthel Yep, the problem we're discussing here is a very good one to have :-). If you feel that C++ > 98 is within the scope of clib2 then I...

I don't really see 68k as a big problem. There's an upside to it as well, keeping 68k means more users and users are the best testers. Of course this...

@obarthel I also feel a bit uneasy when I see wchar* (especially if Amiga shows up in the same sentence). I have no clue how to test the clib plumbing...

> Since the gcc's 68k backend has been modernized in the meantime it may be worthy to look at it again. Whether modern C++ applications can run on a 68k...

@afxgroup You can always #ifdef an entire function (within reason of course) if it becomes to complex. It might also be worth it to look at how these type of...

One way of managing variability could be to use a well thought out directory structure. It's very flat as it is now, there are pros and cons to this of...

@kas1e No point in being thread safe when you're not doing any threading :) The thread safe builds use semaphores in low level stdlib functions like malloc and so on....

@afxgroup Sure, it's open source, forking is an option. But the spark in this discussion was kas1e:s fear that forks will create confusion and I agree with him. It's just...

> Am 02.02.21 um 19:30 schrieb Ola Söder: > Since the gcc's 68k backend has been modernized in the meantime it may be worthy to look at it again. Whether...

@obarthel I opened two more PRs by the way, bugfixes that should be useful to everyone.