Axolotl wrote:
...
I think that too high expectations now are just as premature as concerns or fears.
...
I think everyone understands that. But everyone is having fun, too. Movement is always a good thing.
And trust is always a good thing, too. We trust Fred and the team.
We believe it will be fun, so we're all still on this forum, and some of us are also on SB
I also hope Fred is enjoying the REINVIGORATION of a new project
(personally I've found it difficult to work on a project year after year, I have to take my hat off to Fred for how long he's been developing Purebasic, but this really is a NEW PROJECT for Fred so hopefully he'll enjoy the fresh challenges)
On the contrary ... welcome a C compiler which can compile smaller and faster code than 99% of Purebasic coders can write, even in assembly. C compilers will even let you decide between small and fast code - PB can't. PB is not an optimising compiler ... C compilers are! This really will take PB code compilations up to a whole new level. Don't be afraid, this will be awesome, and give us state-of-the-art compilations.
Also, consider this ... Apple had gone from PowerPC to Intel in just a few years, and now from Intel to ARM in just a few years ... do we really want Fred spending so much time developing a new asm platform every time Apple changes its mind on which architecture to use? (taking away time from all other development). With a C backend, ALL of those platforms can be/ARE supported. This means Fred will have more time to develop for _all of Purebasic_ rather than just Purebasic for one architecture.
Imho asm will most likely be supported in some way or the other looking at what is out there.
It aint as pretty but whatever i dont see a big issue.
And writing a lib with you fav assembler will always be possible.
yes, C supports inline asm. and yes, you'd still be able to compile object files and libraries in asm and include them in PB, just as you already can (C already has this capability)
The problem is ... C is not C.
Or, I know many codes from one C compiler which are not compilable with an other C compiler without manual tweaking.
So Fred will run into an other problem: find a C compiler which fits on the different OSs and CPUs
I think in the Linux world it will be gcc, not really the best compiler.
But that will be not a reason for me to give up PB coding
infratec wrote:The problem is ... C is not C.
Or, I know many codes from one C compiler which are not compilable with an other C compiler without manual tweaking.
So Fred will run into an other problem: find a C compiler which fits on the different OSs and CPUs
As Plan A was LLVM wouldn't the most likely answer to this question be Clang?
That way you'd still indirectly be getting the advantages that made LLVM interesting in the first place.