ok as one of the final few things before an efl 1.0.0... we need to cease the
formatting wars/hell. the first step is in stopping the newlines, space vs tab
and other indentation etc. wars. from now on all efl and e code will conform to
a SINGLE standard. that standard is now programmatically enforced by the config
+ script + tool in the FORMATTING dir. its a tool called uncrustify. it
butchers code much less than indent does and does a good job. to set the tool
just run formatefl.sh from the FORMATTING dir. you can read the script to see.
but from now on ALL commits will be required to be formatted before you commit
(or update for that matter). this stops format arguments. there is only 1
format. feel free to teach your editor to try and do the same format. as such
in jed it's easy. add these to your ~/.jedrc:

USE_TABS           = 0;
C_INDENT           = 3;
C_BRACE            = 2;
C_BRA_NEWLINE      = 0;
C_Colon_Offset     = 0;
C_CONTINUED_OFFSET = 3;
        
for vim, emacs etc. users - feel free to share whatever it is you do to get as
close to the formatting style as possible. this doesn't cover other elements in
standards like using brackets instead of relying on order of operation. i.e. :
  if (a == b && c == d)
is wrong in EFL. it should be
  if ((a == b) && (c == d))

the same with math ops:
  a = b + c / d % e;
should be:
  a = (b + c) / (d % e);
for example.

brackets cost nothing runtime and they explain the actual intended order of
logic. even if you get things right with knowing the order of every operator -
you may forget some of them and your intended logic is never written in the
code. we can go on about other things too, but this uncrustification is a first
step in prettying up the code and making sure we dont have lots of "fix
formatting" stuff in the long run, and we have a defined standard for people
to format their code to when providing patches.

right now i started with eet - that's the first guy to get the treatment. this
will work its way through e + efl over the next week or so. so be warned. once
something has been re-formatted to these rules - stick to them. there is the
script:
  formatefl.sh ./src

for example, will recursively find all src files and reformat them. this is, of
course, for c/c++ code only at this stage.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to