Ocinine is our participation to a Channel 9 contest. Ocinine is the perfect name to understand what we want to do. Ocinine (read OC9) means 'Open channel 9'. Our goal is to make avalaible the media content of Channel 9 to any 'Host Application'. Follow us as we create the new way to see Channel 9.


Coding style

There is no "one true style", but coding style can generate lots of comments. Larry Osterman have 9 post about it and it has generate lots of comments. So Fneuch came from the java world and is coding style look like this :

int main() {
if (a == 100) {

And I came from the C++/MFC world, so my coding style is more like that :

int main()
if (a == 100)

We will use is style for our project, but that will be tough for me !


  • At 11/4/06 19:36, Blogger Fneuch said…

    I don't know how the coding style are seen in a .Net world but in Java we didn't even talk about style, we talk about «Code standards»!

    First of all, it was a convention. Sun suggested a style of coding. It was largely adopted by the community. (You could see it here, here and here.)
    A lot of book were published (the best one here)
    Even tools where created to verify the standard (look at Checkstyle)
    Now, we call it «Code standards»!

    As everyone know, Java is older then C#! So follow the older ;)

  • At 12/4/06 08:33, Blogger Cromag said…

    Il y a un "standard" pour le C# ici :


    Je ne me souviens pas si FXCop gère ça aussi... À suivre...

    Pour les "bracers" en bout de ligne ou sur une nouvelle ligne et les tabs à 2, 3, 4, 8, etc. je ne crois pas que cela puisse être un standard, mais un style. Personnellement je préfère du code plus espacé, donc plus lisible pour moi, c'est mon style. Pour nommer les fonctions, les variables, les classes, etc., ça c'est un standard.

    Style, standard ou convention, là est la question !

    Si Larry à pu faire 9 posts sur le sujet, c'est que les standards ne doivent pas encore faire l?unanimité.


Publier un commentaire