Contributed by merdely on from the you-down-with-pcc-yeah-you-know-me dept.
Ray Lai writes about Theo and Otto's interview over at The Jem Report:
A few weeks ago, the OpenBSD Project announced that the Portable C Compiler (PCC) had been added to the OpenBSD source tree. There has already been some explanation of why the traditional GNU Compiler Collection (GCC) is troublesome and why a new compiler is needed, but there are still some details left uncovered. In this interview, Theo de Raadt and Otto Moerbeek of the OpenBSD Project offer more information about PCC and GCC and where they are headed within the project.
Read the complete interview!
(Comments are closed)
By Karl Sjödahl (Dunceor) dunceor@gmail.com on
Very interesting at least!
Comments
By Ray Percival (sng) on http://undeadly.org/cgi?action=search&sort=time&query=sng
>
> Very interesting at least!
The interview was pretty clear on what to expect in the near future. That would be "nothing".
Comments
By Anonymous Coward (203.20.79.132) on
> >
> > Very interesting at least!
>
> The interview was pretty clear on what to expect in the near future. That would be "nothing".
You mean like how OpenBSD never eventuated? Or how OpenSSH never really materialized? Oh and how about pf! Pfft, nothing come of that hey! And OpenBGP, OpenCVS and OpenNTP were nothing more than glints in some dev wannabe's eye... right?
Yeah, nothing will probably come from OpenBSD+PCC.
Comments
By Karl Sjödahl (Dunceor) on
> > >
> > > Very interesting at least!
> >
> > The interview was pretty clear on what to expect in the near future. That would be "nothing".
>
> You mean like how OpenBSD never eventuated? Or how OpenSSH never really materialized? Oh and how about pf! Pfft, nothing come of that hey! And OpenBGP, OpenCVS and OpenNTP were nothing more than glints in some dev wannabe's eye... right?
>
> Yeah, nothing will probably come from OpenBSD+PCC.
>
He didn't say that nothing would come out of PCC, he said that nothing would come out of PCC in the near future. Big difference.
Ray Percival: Well it wasn't that clear on it but maybe you are right. We'll just have to wait and see.
By tedu (204.14.154.69) on
> > >
> > > Very interesting at least!
> >
> > The interview was pretty clear on what to expect in the near future. That would be "nothing".
>
> You mean like how OpenBSD never eventuated? Or how OpenSSH never really materialized? Oh and how about pf! Pfft, nothing come of that hey! And OpenBGP, OpenCVS and OpenNTP were nothing more than glints in some dev wannabe's eye... right?
>
> Yeah, nothing will probably come from OpenBSD+PCC.
yeah, ray must be mistaken. i'm sure pcc will be the compiler for openbsd 4.3.
Comments
By Anonymous Coward (203.20.79.132) on
> >
> > You mean like how OpenBSD never eventuated? Or how OpenSSH never really materialized? Oh and how about pf! Pfft, nothing come of that hey! And OpenBGP, OpenCVS and OpenNTP were nothing more than glints in some dev wannabe's eye... right?
> >
> > Yeah, nothing will probably come from OpenBSD+PCC.
>
> yeah, ray must be mistaken. i'm sure pcc will be the compiler for openbsd 4.3.
Yes, sorry. I misinterpreted that badly.
By Anonymous Coward (128.171.90.200) on
By Anonymous Coward (199.18.139.74) on
By justwords (84.18.238.22) on
"What other hurdles remain in replacing GPL-licensed programs in OpenBSD?
TdR: But that's never really been the agenda, see. Some people think we hate GNU code. But the thing is we hate large code, and buggy code that upstream does not maintain. That's the real problem"
Comments
By William Palmer (wcpalmer) on http://wcpalmer.com
>
> "What other hurdles remain in replacing GPL-licensed programs in OpenBSD?
>
> TdR: But that's never really been the agenda, see. Some people think we hate GNU code. But the thing is we hate large code, and buggy code that upstream does not maintain. That's the real problem"
I've actually been wanting to look into compiler design/theory, but I'm terrified of GCC's codebase. I've only heard bad things about it.
I think, to prevent permanent scarring/damage, I may take a look at PCC instead.