Re: Linux Kernel include files

2007-06-21 Thread Arnd Bergmann
On Friday 22 June 2007, [EMAIL PROTECTED] wrote: > this has been discussed many times and the answer is that the kernel is > not gong to change it's side of things to ANSI C. I don't think that's entirely true with regard to the include files. We have always tried not to step on anyone's toes

Re: Linux Kernel include files

2007-06-21 Thread Arjan van de Ven
ason is that in order to support Linux specific features, you > need > to include Linux specific include files (the Linux kernel include files). I assume you typoed and meant "cleaned up kernel include files as installed by make headers_install" instead. > As > th

Re: Linux Kernel include files

2007-06-21 Thread Joerg Schilling
[EMAIL PROTECTED] wrote: > On Fri, 22 Jun 2007, Joerg Schilling wrote: > > > Is there some hope that at least the Linux kernel interface definition > > files and > > everything recursively included from these files will be rewritten in > > vanilla > > ANSI C? > > this has been discussed many

Re: Linux Kernel include files

2007-06-21 Thread david
On Fri, 22 Jun 2007, Joerg Schilling wrote: Is there some hope that at least the Linux kernel interface definition files and everything recursively included from these files will be rewritten in vanilla ANSI C? this has been discussed many times and the answer is that the kernel is not gong

Linux Kernel include files

2007-06-21 Thread Joerg Schilling
ools. Why does this happen? Well, the reason is that in order to support Linux specific features, you need to include Linux specific include files (the Linux kernel include files). As these include files are currently not written in vanilla (ANSI) C but in a GCC-C-variant, other compilers d

Linux Kernel include files

2007-06-21 Thread Joerg Schilling
this happen? Well, the reason is that in order to support Linux specific features, you need to include Linux specific include files (the Linux kernel include files). As these include files are currently not written in vanilla (ANSI) C but in a GCC-C-variant, other compilers do not like

Re: Linux Kernel include files

2007-06-21 Thread david
On Fri, 22 Jun 2007, Joerg Schilling wrote: Is there some hope that at least the Linux kernel interface definition files and everything recursively included from these files will be rewritten in vanilla ANSI C? this has been discussed many times and the answer is that the kernel is not gong

Re: Linux Kernel include files

2007-06-21 Thread Joerg Schilling
[EMAIL PROTECTED] wrote: On Fri, 22 Jun 2007, Joerg Schilling wrote: Is there some hope that at least the Linux kernel interface definition files and everything recursively included from these files will be rewritten in vanilla ANSI C? this has been discussed many times and the

Re: Linux Kernel include files

2007-06-21 Thread Arjan van de Ven
to support Linux specific features, you need to include Linux specific include files (the Linux kernel include files). I assume you typoed and meant cleaned up kernel include files as installed by make headers_install instead. As these include files are currently not written in vanilla (ANSI) C

Re: Linux Kernel include files

2007-06-21 Thread Arnd Bergmann
On Friday 22 June 2007, [EMAIL PROTECTED] wrote: this has been discussed many times and the answer is that the kernel is not gong to change it's side of things to ANSI C. I don't think that's entirely true with regard to the include files. We have always tried not to step on anyone's toes

Re: Linux Kernel include files

2007-06-21 Thread David Woodhouse
On Fri, 2007-06-22 at 01:38 +0200, Joerg Schilling wrote: The main problems are not really hard to fix.. - Most problems eem to be related to the fact that Linux does not use C-99 based types in the kernel and the related type definitions are not written in plain C. This

Re: Linux Kernel include files

2007-06-21 Thread H. Peter Anvin
David Woodhouse wrote: The main problems are not really hard to fix.. -Most problems eem to be related to the fact that Linux does not use C-99 based types in the kernel and the related type definitions are not written in plain C. This is something that should be fixed

<    1   2