Hello,
if you've been wondering what the heck are the...
--cut--
// Attributes:
// eca-style-version: 3
--cut--
... segments at the start of .cpp source files, there's now some info
about this in the programmer's guide:
--cut--
Style updates
-------------
The general rule is to use consistant style within one
source file (i.e. compilation unit). Updates to style issues
are also done with the same granularity. The following global
updates have been made so far to the sources:
eca-style-version: 1
The opening braces of multi-line functions should be put on a separate
line, at column 1, instead of being on the same line with
function signature. This change only applies to functions, IOW
the K&R style is followed.
eca-style-version: 2
Extra parenthesis around "return" values should be removed.
eca-style-version: 3
The module name prefix, for example "(eca-session) ", should
be removed from ECA_LOG_MSG() statements.
If a file has been updated according to these guidelines,
the appropriate style version should be mentioned at the
start of the file ("Attributes: eca-style-version: XXX").
--cut--
IOW, not very significant stuff, but just something that's needed to keep
the codebase clean.
-- links, my public keys, etc at http://eca.cx/kv ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Ecasound-list mailing list Ecasound-list@email-addr-hidden https://lists.sourceforge.net/lists/listinfo/ecasound-listReceived on Fri Aug 19 04:15:07 2005
This archive was generated by hypermail 2.1.8 : Fri Aug 19 2005 - 04:15:08 EEST