Search results

Create the page "Coding style," on this wiki! See also the search results found.

Page title matches

• Coding style
  ...with some additional elements from the GNU coding standards and the SunOS coding standards. * [[Coding style/Formatting|Formatting]]
  4 KB (567 words) - 13:59, 2 February 2016
• Coding style/Formatting
  ...style considerations apply to the most mechanical aspects of C source code style. ...the more difficult ones to adopt in a non-disruptive manner. See [[Coding style/Transition strategies]] for one possibility.
  14 KB (2,049 words) - 11:18, 19 October 2012
• Coding style/C
  ...s to archive its Talk page. The actual content has been moved to [[Coding style]].
  98 bytes (17 words) - 14:53, 14 April 2008
• Coding style/C/Formatting
  #REDIRECT [[Coding style/Formatting]]
  37 bytes (4 words) - 12:14, 11 April 2008
• Coding style/Practices
  * Always declare function return types. Use ANSI C-style function definitions. /* bad style */
  27 KB (4,209 words) - 15:21, 22 September 2024
• Coding style/Transition strategies
  Parts of the existing source tree are not conforming to our coding style. These inconsistencies can create barriers to entry for new contributors. To mark files as having indentation conforming to our coding style, add <code>c-basic-offset: 4</code> to the local variable line:
  2 KB (288 words) - 01:02, 3 November 2009
• Coding style/Reindenting
  ...e> cleans up mixtures of spaces and tabs anywhere on a line, while the new-style one only does so inside indentation whitespace.) ...tions Emacs file-local variable settings to mark what sort of C formatting style a given source file conforms with, as well as for controlling the operation
  12 KB (1,826 words) - 19:24, 14 October 2011
• Coding style/Version control practices
  Style and naming changes to ASN.1 encoder
  5 KB (894 words) - 16:22, 7 December 2015
• Coding style/Style checker
  ...ized return statement just to placate the checker. Nonetheless, using the style checker and intelligently interpreting its output will usually reduce the t If emacs is installed, the style checker will detect indentation issues, but will run much more slowly.
  2 KB (379 words) - 18:35, 29 April 2017

Page text matches

• Release Meeting Minutes/2009-06-23
  Coding Styles and Transition Strategies * Discussed methods of enforcing style rules.
  4 KB (734 words) - 23:57, 3 January 2011
• Main Page
  * [[Coding style]]
  3 KB (441 words) - 18:02, 3 January 2017
• Coding style
  ...with some additional elements from the GNU coding standards and the SunOS coding standards. * [[Coding style/Formatting|Formatting]]
  4 KB (567 words) - 13:59, 2 February 2016
• How to contribute
  * Coding style ...l of Style] when appropriate. There are probably aspects of the Wikipedia style that are not suitable for K5Wiki, but we can identify those here as we beco
  1 KB (218 words) - 11:27, 3 April 2008
• Coding style/Formatting
  ...style considerations apply to the most mechanical aspects of C source code style. ...the more difficult ones to adopt in a non-disruptive manner. See [[Coding style/Transition strategies]] for one possibility.
  14 KB (2,049 words) - 11:18, 19 October 2012
• Coding style/C
  ...s to archive its Talk page. The actual content has been moved to [[Coding style]].
  98 bytes (17 words) - 14:53, 14 April 2008
• Release Meeting Minutes/2008-05-05
  Publish better coding standards/guidelines Static Analysis Tools: Tools prefer a specific coding style. Using that style avoids false positives and makes the tools more useful.
  4 KB (649 words) - 17:39, 10 January 2011
• KrbWeb Outline of Work
  ...lar use case. This is often cited as the rationale for the specifications' style of unconstrained XML element extensibility (in contrast to ID-WSF's constra ...ble during the initial deployments on low-value applications (such as hard-coding secrets into applications), are not appropriate for higher-value applicatio
  99 KB (14,634 words) - 19:15, 29 October 2008
• Coding style/Transition strategies
  Parts of the existing source tree are not conforming to our coding style. These inconsistencies can create barriers to entry for new contributors. To mark files as having indentation conforming to our coding style, add <code>c-basic-offset: 4</code> to the local variable line:
  2 KB (288 words) - 01:02, 3 November 2009
• Roadmap
  * Increase conformance to coding style
  5 KB (580 words) - 18:06, 3 January 2017
• Contributing code
  ...e the [[Coding style/Style checker|style checker]] script to help minimize style issues. Changes must be made against the master branch, not a release bran
  2 KB (370 words) - 14:45, 4 March 2014
• Release 1.8
  * Increase conformance to coding style ** See [[Coding style/Transition strategies]]
  2 KB (190 words) - 16:48, 3 March 2010
• Application Maintenance
  ...defined coding style for this project. Please follow the dominant coding style of the file you are modifying.
  1 KB (231 words) - 13:26, 22 December 2015
• Git migration
  * [[Coding style/Version control practices]]
  3 KB (484 words) - 13:02, 5 July 2012
• Getting source code
  ...ted in contributing changes to our repository, please consult our [[Coding style/Version control practices | version control practices]] page. You should of
  2 KB (264 words) - 16:21, 14 December 2021
• Cleanups
  * lib/gssapi/mechglue should use the MIT krb5 style, not the Solaris coding style with tabs. ** The file uses K&R-style function definitions.
  12 KB (2,019 words) - 02:40, 29 July 2023

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)