search for: styleguid

hy there, I hope as on http://wiki.centos.org/SpecialInterestGroup/Artwork mentioned I'm here at the right place for that. It also fits for the Promo SIG or others Under http://www.braincache.de/centos/CentOS_Styleguide_0.1-draft.pdf can be my first idea of an Styleguide wich could help to give a line of usage to some Grafics & design issues also as for Promo Stuff. I also have made a Banner http://www.braincache.de/centos/banner001.jpg how about other ideas? Comments? What about some slogans? What about &...

Perhaps most of you have already seen this? http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html Comments/Critiques? Thanks, Esmail ps: Reminds me of PEP 8 for Python http://www.python.org/dev/peps/pep-0008/ Maybe not that surprising since Python is also one of the main languages used by Google.

Probably this has come up before... but have we considered just adopting the Google style guidlines and maybe modifying it in some places? They have a nice script for c++ which will check for many things. http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py

...rrible. It is an atrocity. It is everything that is bad about trying to "parse" C++ with regular expressions and python hacks, built up w/o any overarching design or cohesion over years. I await the day we can kill it off and use a real Clang-based tool instead. > > http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml > > http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mail...

...ility of code which changes behavior depending on whether the full or forward decl are available (which, then, may be an ODR-violation). Effectively the same reasons why the standard forbids users from forward-declaring std:: names apply to doing so to user-defined names. https://google.github.io/styleguide/cppguide.html#Forward_Declarations lists some of the issues, and a recommendation not to do so. Of course you do have the upside is that it can improve compile time. Which is certainly of value, and perhaps that's a worthwhile trade-off when the implementation and forward-declare are both wit...

...e.phabricator.com/book/phabricator/article/arcanist_lint/). This will enforce the check when `arc diff` is run (reviewers wouldn't see the warnings though). There are two linters we might be interested in enabling: - cpplint (code style checker based on cpplint.py <https://github.com/google/styleguide>) - cppcheck (C++ linter based on cppcheck <http://cppcheck.sourceforge.net/>) Note that cpplint assumes google code style, but I think it can potentially be replaced it with clang-format with configurable code styles. On Wed, Nov 16, 2016 at 12:28 PM Eric Liu <ioeric at google.com&g...

...behavior depending on whether the full or forward decl are available > (which, then, may be an ODR-violation). > > Effectively the same reasons why the standard forbids users from > forward-declaring std:: names apply to doing so to user-defined names. > > https://google.github.io/styleguide/cppguide.html#Forward_Declarations > lists some of the issues, and a recommendation not to do so. > > Of course you do have the upside is that it can improve compile time. > Which is certainly of value, and perhaps that's a worthwhile trade-off when > the implementation and forw...

...of such a transition, or how to get from here to there, but rather, if there is a better place to be. My arguments for the change are: 1. No other popular C++ coding style uses capitalized variable names. For instance here are other popular C++ conventions that use camelCase: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml http://www.c-xx.com/ccc/ccc.php http://geosoft.no/development/cppstyle.html And, of course, the all-lower-case conventions (e.g. C++ ARM) don’t capitalize variable names. In addition, all the common C derived languages don’t use capitalized variable na...

...rns and suggestions for your patch, > Hi Chris, Thanks for the reply. Indeed, some of your comments to safecode patch apply here. Codingstyle: I'll try to cleanup as much as I can today. Do you have any lint-like tool that checks for llvm coding style (similar to cpplint <http://google-styleguide.googlecode.com/svn/trunk/cpplint/>)? Documentation: everything is in the wiki. The main pages are: http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer http://code.google.com/p/address-sanitizer/wiki/AddressSanitizerAlgorithm "who is going to maintain": my team at Google...

.../or R FAQ? -- Bert On Tue, May 17, 2011 at 4:07 PM, <Bill.Venables at csiro.au> wrote: > Amen to all of that, Bert. ?Nicely put. ?The google style guide (not perfect, but a thoughtful contribution on these kinds of issues, has avoiding attach() as its very first line. ?See http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html) > > I would add, though, that not enough people seem yet to be aware of within(...), a companion of with(...) in a way, but used for modifying data frames or other kinds of list objects. ?It should be seen as a more flexible replacement for trans...

On Jun 21, 2011, at 8:05 AM, Kostya Serebryany wrote: > Hi, > What would be our next steps in getting ASan into the LLVM trunk? > I'd like to do it in two steps, first for the LLVM part with minimal tests and then for the run-time library and all tests. > The current ASan's source repository will probably stay the primary home for the run-time library and tests as we plan

...nt/). This >> will enforce the check when `arc diff` is run (reviewers wouldn't see the >> warnings though). >> >> There are two linters we might be interested in enabling: >> - cpplint (code style checker based on cpplint.py >> <https://github.com/google/styleguide>) >> - cppcheck (C++ linter based on cppcheck <http://cppcheck.sourceforge.net/>) >> >> Note that cpplint assumes google code style, but I think it can potentially >> be replaced it with clang-format with configurable code styles. >> >> On Wed, Nov 16...

...tematic and consistent guide is important for programming, so does in R. Here are some recommended style guides for programming in R. Pick one of them and strictly follow it. 1. Google''s R Style Guide * Link to Google''s R Style Guide (official URL <http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html>,pdf <http://piboonrungroj.files.wordpress.com/2012/06/googles-r-style-guide.pdf>) * Providing 14 R Style Rules including filenames, identifiers, indentation, spacing etc. /"These rules were designed in collaboration with the...

...as base? Google/LLVM/Mozilla/Webkit/Chromium - Samples present in repo <https://github.com/nigelbabu/clang-format-sample>. *NOTE*: Samples generated with indent as 4 spaces. - Google Style Guide <https://google.github.io/styleguide/cppguide.html> - LLVM Style Guide <http://llvm.org/docs/CodingStandards.html> - Mozilla Style Guide <https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style> - WebKit style guide <https://webkit.org/code-style-...

...gt; > Hi Chris, > > Thanks for the reply. > Indeed, some of your comments to safecode patch apply here. > > Codingstyle: I'll try to cleanup as much as I can today. > Do you have any lint-like tool that checks for llvm coding style (similar > to cpplint <http://google-styleguide.googlecode.com/svn/trunk/cpplint/>)? > I don't know of any effective ones. Kostya, maybe you can send the code by myself and/or Nick to help walk through it for style issues? Documentation: everything is in the wiki. The main pages are: > http://code.google.com/p/address-sanitizer/w...

...=Puio5dly9N8#t=12m12s - https://www.youtube.com/watch?v=Puio5dly9N8#t=42m40s Other coding guidelines already embrace this: - http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-signed - http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Res-unsigned - https://google.github.io/styleguide/cppguide.html#Integer_Types It is rare that overflowing (and wrapping) an unsigned integer won't trigger a program bug when the overflow was not intentionally handled. Using signed arithmetic means that you can actually trap on over/underflow and catch these bugs (when using fuzzing for insta...

Hi List, I have been asked in this thread if I would contribute an article on iptables to the Wiki: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=10240&forum=37 The article would be based on a tutorial I have previously written here: http://forums.pcper.com/showthread.php?t=432469 I'm not sure where the article should best go so leave that to your discretion. If you

On 11/14, Mehdi Amini via llvm-dev wrote: > Ideally I’d even really like to have a both checking for revision on > phab, clang-formatting them, and post a comment when there is a > mismatch :) I'd like that! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Digital signature URL:

...>> Thanks for the reply. >> Indeed, some of your comments to safecode patch apply here. >> >> Codingstyle: I'll try to cleanup as much as I can today. >> Do you have any lint-like tool that checks for llvm coding style (similar >> to cpplint <http://google-styleguide.googlecode.com/svn/trunk/cpplint/> >> )? >> > > I don't know of any effective ones. Kostya, maybe you can send the code by > myself and/or Nick to help walk through it for style issues? > > Documentation: everything is in the wiki. The main pages are: >> ht...

Hola, ¿qué tal? Hace poco vi que Google había hecho pública su guía de estilo interna para programar en R: http://google-styleguide.googlecode.com/svn/trunk/google-r-style.html Me tomé la libertad de traducirla: http://datanalytics.com/guia_estilo_r.html Cuanto más pienso en ella, más carencias veo. Escribí sobre ello en mi blog ( http://www.datanalytics.com/blog/2010/11/01/una-propuesta-de-guia-de-estilo-de-r/ ). Las do...