Re: [Texmacs-dev] Coding guidelines

[Miguel de Benito Delgado]

Hi,

  even though I usually follow different conventions, I'll stick to those when submitting changes (in spanish we have a proverb that goes "wherever you go, do as you see others do", though I don't heed it that much), please forgive any slips (won't there be many, I promise). And I will certainly do separate updates for the cosmetic stuff.

  About the long lines, however, should I really cut at 80 chars? I used to do it, but with newer screens around 2000px wide on average, it seems a bit unnecessary. On the other hand, narrower editor windows allow for more editor windows side to side... Ok, forget it, 80 columns it is.

 My savannah.gnu.org user id is mdbenito. Thanks, Oh, Joris! I shall make wise use of the powers you have bestowed upon me...

Bye,

________________
Miguel de  Benito.

On Sun, Nov 7, 2010 at 15:32, Joris van der Hoeven <address@hidden> wrote:

Hi all,

In reply to Miguel's request for our coding guidelines:

as far as Qt is concerned, best is to follow Max' style
as much as possible, ..., except when it comes to spacing ;^)

Indeed, in an 80-columns wide Emacs editor, very long lines
are not very nice, and it would be best to follow Emacs'
conventions for indentation. I personally also avoid
unnecessary whitespace, and use as much as possible
the following kind of spacing:

   int i= 123; // no space before =, but one space after
   if (a == b || b == c)
     blah_blah (); // no need for {, }
   result= f (x, y, z) + c; // space before ( but not after,
                            // space after , ) but not before.
   /************************ ... **
   * Block of explanations
   ************************* ... /*

Miguel: But, as Max suggested, please submit such cosmetic changes
in separate patches. If you have an account on Savannah,
then please give me your ID, so that you can commit directly
to the SVN server.

Best wishes, --Joris