Andre Poenitz <[EMAIL PROTECTED]> writes:
| Index: Rules
| ===================================================================
| RCS file: /usr/local/lyx/cvsroot/lyx-devel/development/Code_rules/Rules,v
| retrieving revision 1.14
| diff -u -p -r1.14 Rules
| --- Rules 25 Sep 2002 14:26:09 -0000 1.14
| +++ Rules 23 Oct 2003 11:10:44 -0000
| @@ -293,12 +279,9 @@ Formatting
|
| * Formatting
|
| - - Please adapt the formatting of your code to the setting in LyX in that
| - particular file. Lars and Asger are slowly, but surely moving the source
| - towards Linux kernel style formatting, aka K&R style. We suggest that you
| - also do this, but this is NOT something that has been decided generally.
| - (a pity - jbl)
| -
| + - Adapt the formatting of your code to the one used in the
| + other parts of LyX. In case there is different formatting for
| + the same construct, use the one used more often.
agree.
| * Use existing structures
|
>
| Moreover I'd like to replace the comment on braces to explicitly allow
| short single statement bodys of the innermost 'if', 'else', 'for' etc
| to go without braces. I.e.
>
| if (pos == par.size())
| --pos;
>
| and
>
| if (first) {
| while (first < last && par.isHfill(first))
| ++first;
| }
>
| and
>
| if (pos >= row.endpos()) {
| for (pos_type i = row.pos(); i < pos && !par.isHfill(i); ++i)
| return false;
| }
>
| should be 'legal'.
ok.
| [Note that this is already _much_ weaker than my favourite 'drop braces
| where not necessary']
I know.
--
Lgb
