I usually prefer (as you can see i the first link) the continuation line "Aligned with opening delimiter" that is:
> + Yes: > + foo = long_function_name(var_one, var_two, > + var_three, var_four) > + No: > + foo = long_function_name( > + var_one, var_two, > + var_three, var_four) But there isn't a real efl guideline on this, so technically you are free to use the indentation you like more. If you are working on existing efl code just follow the first rule from the wiki: ALWAYS KEEP EXISTING CODING STYLE. Hope I'm not starting a new flame-war :) bye 2016-12-12 11:48 GMT+01:00 Shuhrat Dehkanov <[email protected]>: > Hello, > > Yes, I googled. The most relevant link that came up > https://sourceforge.net/p/enlightenment/mailman/message/33443401/ > seems to talk only about Mussolini. So, not much of a help. > Nothing much at https://phab.enlightenment.org/w/ecoding/#coding-style > either. > Existing code seems to use varying sizes as 3, 4, 6, 9, 44(!) spaces. > > So, what's the "preferred" size for continuation indent? > > ------------------------------------------------------------ > ------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
