From: Learning on
I done some searching but was hoping to get the "gurus"
advice in the group. I'd like to start writing parts
of my own code into the linux kernel. (Most likely
using the Debian 4.0r2 release). Is standard or ISO
C about the same as GCC C or should I stick strictly
with GCC standards? Thanks for your replies.
From: Ian Collins on
Learning wrote:
> I done some searching but was hoping to get the "gurus"
> advice in the group. I'd like to start writing parts
> of my own code into the linux kernel. (Most likely
> using the Debian 4.0r2 release). Is standard or ISO
> C about the same as GCC C or should I stick strictly
> with GCC standards? Thanks for your replies.

See the Linux kernel coding standards, I don't know where they are
documented, but they will exist.

--
Ian Collins.
From: roblevintennis on
On Jan 7, 8:05 pm, Ian Collins <ian-n...(a)hotmail.com> wrote:
> Learning wrote:
> > I done some searching but was hoping to get the "gurus"
> > advice in the group. I'd like to start writing parts
> > of my own code into the linux kernel. (Most likely
> > using the Debian 4.0r2 release). Is standard or ISO
> > C about the same as GCC C or should I stick strictly
> > with GCC standards? Thanks for your replies.
>
> See the Linux kernel coding standards, I don't know where they are
> documented, but they will exist.
>
> --
> Ian Collins.

There are some differences which you will need to read about by doing
some searching. But if you're trying to meet a certain standard, gcc
will let you compile with -std=c89 or -std=c99, etc. From doing a gcc
--help:
-std=<standard> Assume that the input sources are for
<standard>
You can also look at some of the other options available and see if
they meet your needs. From what I remember, gnu tries a little harder
to me c89 then c99, but I'm not the guru you asked for LOL, so
hopefully you'll get a more definitive answer soon...hope that at
least helps.
 | 
Pages: 1
Prev: Compiling multiple files
Next: queue code