Re: non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?)

Tim Riker
2000-11-02T20:59:55Z

ok, a very valid point. The "C++ kernel code" reference is very telling.
(ouch). ;-)

Obviously the changes to support non-gcc compilers should have the goal
of minimal impact on gcc users lives. I recognize that the mainstream
will still use gcc.

Q: Why should we help you make it possible to use a proprietary C
compiler?

This is right on the money. I hope to show that is is all part of "World
Domination". ;-) I can easily see other paths to get there though, so
why this one?

As is being discussed here, C99 has some replacements to the gcc syntax
the kernel uses. I believe the C99 syntax will win in the near future,
and thus the gcc syntax will have to be removed at some point. In the
interim the kernel will either move towards supporting both, or a
quantum jump to support the new gcc3+ compiler only. I am hoping a
little thought can get put into this such that this change will be less
painful down the road.

I hope that I can lend some time to this project and save the rest of
the community time in the long run. Benefit our projects in the short
term. And impact the rest of the linux-kernel community as little as
possible in the short term.

How does that sound for a way forward?

"Theodore Y. Ts'o" wrote:
>
> Date: Thu, 02 Nov 2000 12:31:51 -0700
> From: Tim Riker <Tim@Rikers.org>
>
> Me or Alan? I did not mean this as a dig. I feel strongly that one
> should have the choice here. I do not choose to enforce my beliefs on
> anyone else. I am suggesting only that others should provide the same
> courtesy. I truly meant "Thank you for you opinion". I feel the
> community benefits from the differing opinions contained within it.
>
> Yes, but that argument doesn't hold once you start asking the everyone
> to work on making that choice available. The question that some part of
> the community may ask is --- why should we help you make it possible to
> use a propietary C compiler?
>
> Choice also implies a choice not to work on things which help some
> particular person's pet cause, whether that is C++ kernel code, or
> propietary C compilers. If it makes the code harder to maintain or more
> complex, it impacts everyone, and it's fair to ask the question whether
> or not the feeling "one should have the choice here" is worth the cost
> which you're asking everyone to bear.
>
> - Ted

--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.