WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have
preserved to ensure that existing links to archives are not broken.
The live archive, which contains the latest emails, can be found at
http://lists.xen.org/

On 6/25/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> On Sunday 26 June 2005 02:45, aq wrote:
> > looks like this patch (and also many other codes in the tree) mixed of
> > tabs and spaces for indentation :-(. especially this code will be in
> > mainline in the future.
> >
> > is it time for us to have a official *coding style guide*, and all the
> > patches sent in must comply with the guide in order to be picked up
> > ???
>
> It seems sensible for XenLinux code to follow the Linux CodingStyle document
> (although I'm not sure all the drivers do this yet).
>
> Xen-related C code that isn't destined for the Linux kernel itself has a
> different coding style:
> * we indent in blocks of 4 spaces and don't use tabs
> * { and } are always on a new line, unlike K&R style
> * we put a space between an if and the open parenthesis, and between the
> parentheses and the boolean: if ( murble )
i think it is very bad idea to have 2 coding styles for code in kernel
and out of kernel. because people work on all those code must always
remember to adjust the editor configuration, depend on the code in or
out of kernel, which is a nightmare :-(
how about this simple guide?
- C code complies Linux kernel coding style
- Python code can use (4) spaces for indentation (as in currently)
regards,
aq
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel