harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Tanzer <stru...@guglhupf.net>
Subject [dev-process] Coding Style Guide
Date Fri, 21 Oct 2005 14:58:29 GMT
I've just had a look at some C code from jchevm and BootJVM to compare 
the coding style of both contributions. Both use coding styles which are
quite common for C source code but they are slightly different, and I
don't think that's good. We should really define a coding style guide
before even more code is contributed.

I'm not worried about Java code we write, because I assume everyone
agrees to use the Java Coding Conventions from Sun [1] here. Much of the
development in Harmony is done in C at the moment, and we need a coding
style guide here too.

I once suggested to use the Java Coding Conventions in C and C++ code
too [2] (at least where possible, and we'd have to extend them to cover
pre-processor directives and other C/C++ specific things). We could also
use a style like Archie Cobbs or Dan Lydick used in their contributions,
but IMHO we should write it down and then stick to it.

Mark Wielaard provided a link to the project policy of GNU Classpath 
[3], I guess we could get some Ideas from this too.

Regards, David

[1] http://java.sun.com/docs/codeconv/

David Tanzer, Haghofstr. 29, A-3352 St. Peter/Au, Austria/Europe
http://deltalabs.at -- http://dev.guglhupf.net -- http://guglhupf.net
My PGP Public Key: http://guglhupf.net/david/david.asc
Pinky, Are You Pondering What I'm Pondering?
Umm, I think so Big Brainy Fish Face Stove Pipe Wiggle Room Eileen. 
But if you get a long little doggie, wouldn't you just call it 
a dachshund?

View raw message