Convert tabs to spaces in the libjpeg code and the SIMD code (TurboJPEG retains the use of tabs for historical reasons. They were annoying in the libjpeg code primarily because they were not consistently used and because they were used to format as well as indent the code. In the case of TurboJPEG, tabs are used just to indent the code, so even if the editor assumes a different tab width, the code will still be readable.)
git-svn-id: svn+ssh://svn.code.sf.net/p/libjpeg-turbo/code/trunk@1278 632fc199-4ca6-4c93-a231-07263d6284db
diff --git a/coderules.txt b/coderules.txt
index 357929f..ea8fcc0 100644
--- a/coderules.txt
+++ b/coderules.txt
@@ -21,11 +21,11 @@
*/
We indent statements in K&R style, e.g.,
- if (test) {
- then-part;
- } else {
- else-part;
- }
+ if (test) {
+ then-part;
+ } else {
+ else-part;
+ }
with two spaces per indentation level. (This indentation convention is
handled automatically by GNU Emacs and many other text editors.)
@@ -57,16 +57,16 @@
ansi2knr does not transform method declarations (function pointers in
structs). We handle these with a macro JMETHOD, defined as
- #ifdef HAVE_PROTOTYPES
- #define JMETHOD(type,methodname,arglist) type (*methodname) arglist
- #else
- #define JMETHOD(type,methodname,arglist) type (*methodname) ()
- #endif
+ #ifdef HAVE_PROTOTYPES
+ #define JMETHOD(type,methodname,arglist) type (*methodname) arglist
+ #else
+ #define JMETHOD(type,methodname,arglist) type (*methodname) ()
+ #endif
which is used like this:
- struct function_pointers {
- JMETHOD(void, init_entropy_encoder, (int somearg, jparms *jp));
- JMETHOD(void, term_entropy_encoder, (void));
- };
+ struct function_pointers {
+ JMETHOD(void, init_entropy_encoder, (int somearg, jparms *jp));
+ JMETHOD(void, term_entropy_encoder, (void));
+ };
Note the set of parentheses surrounding the parameter list.
A similar solution is used for forward and external function declarations