similar to: [LLVMdev] Coding standard - indentation width

Hi, The coding standard document doesn't mention anything about preferred indentation width (only not to change per-file and not make massive re-tabbing diffs), but I swear I've had people complain at me for not using 2 spaces in new files I've committed. Am I misremembering, or is there a preferred tabwidth of 2, and if so where is it / should it be documented? Cheers,

On Wed, Feb 29, 2012 at 6:26 PM, James Molloy <james.molloy at arm.com> wrote: > Hi, > > > > The coding standard document doesn’t mention anything about preferred > indentation width (only not to change per-file and not make massive > re-tabbing diffs), but I swear I’ve had people complain at me for not using > 2 spaces in new files I’ve committed. > > > >

According to the LLVM coding standards, Immediately after the header file comment <http://llvm.org/docs/CodingStandards.html#header-file-comment> (and include guards if working on a header file), the minimal list of #includes <http://llvm.org/docs/CodingStandards.html#minimal-list-of-includes>required by the file should be listed. We prefer these #includes to be listed in this order:

The current guidelines [1] on the use of the struct keyword are too restrictive and apparently ignored. They limit the use of struct to PODs, citing broken compilers. The guidelines are out-of-date and should be relaxed. Here’s why: 1. Our updated list of supported compilers should all deal correctly with non-POD structs. 2. A quick grep of the source suggests that no one paid attention

Generally it is safer to include ISO headers first (using the ‘#include <...>’ form) so as to minimise the possibility that a later user declaration or macro definition interferes with the correctness of the Standard libraries. It also tends to make pre-compiled header implementations faster and more shareable across a larger set of files. I would like to suggest revising the LLVM

I am using emacs-21.3 when writing R functions on Linux debian, and I am trying to follow the advice i R-exts.pdf (2.1.1) regarding indentation. That is, I set 'c-default-style' to "bsd" and 'c-basic-offset' to 4. However, while this gives me the intended indentation in C code, it doesn't change the behavior in R code; I still get an indentation of size 2. This is my

On 22/01/16 14:38, Ian Campbell wrote: > Debian bug 812166[0] reported this build failure due to > Wmisleading-indentation with gcc-6: > > non-fatal.c: In function 'init_nonfatal_mce_checker': > non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] > switch (c->x86_vendor) { > ^~~~~~ > >

I use the recommendations in "R coding standards", i.e., I put ;;; C (add-hook 'c-mode-hook (lambda () (c-set-style "bsd"))) ;;; ESS (add-hook 'ess-mode-hook (lambda () (ess-set-style 'C++ 'quiet) (add-hook 'local-write-file-hooks (lambda

Debian bug 812166[0] reported this build failure due to Wmisleading-indentation with gcc-6: non-fatal.c: In function 'init_nonfatal_mce_checker': non-fatal.c:103:2: error: statement is indented as if it were guarded by... [-Werror=misleading-indentation] switch (c->x86_vendor) { ^~~~~~ non-fatal.c:97:5: note: ...this 'if' clause, but it is not if (

A quick coding standards question. The current coding standards doc has helpful guidance on Doxygen comments and the like: https://llvm.org/docs/CodingStandards.html#source-code-formatting One aspect which isn't explicit is the policy on duplicating code comments for subclasses. To modify an example from that doc: """ // In Something.h: /// An abstraction for some complicated

I use Gnu emacs 21, Linux RH9 and R-1.7.0. I have succeeded to get the recommended indentation of 4 in C thru customization as described in 'R-exts', p.73, but I can't get it to work in R code. Can someone help, for instance by sending me the appropriate lines in '.emacs'? Thanks! --- G?ran Brostr?m tel: +46 90 786 5223 Department of Statistics

Hi, I was building LLVM with gcc 6.1.1 recently and it was spitting out some warnings relating to misleading indention that caught my eye. This wasn't a fresh build so I may have missed some. I've CC'ed the authors of the potentially misleading lines so they can decide what do about the warnings (if anything). I'm wondering if clang-format is making some inappropriate choices

I'm using emacs-21.4 on debian unstable, together with the latest ESS implementation. I try to change indentation to 4 by following the advise in "R-exts": It results in the following lines in my .emacs file: (custom-set-variables ;; custom-set-variables was added by Custom -- don't edit or cut/paste it! ;; Your init file should contain only one such instance.

Adjust indentation from spaces to tab (+optional two spaces) as in coding style with command like: $ sed -e 's/^ /\t/' -i */Kconfig Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> --- drivers/gpu/drm/nouveau/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/Kconfig b/drivers/gpu/drm/nouveau/Kconfig index

This patch fixes an indentation error in main.py. The effect of this bug is that block-attach does not check labels if the ACM is active. This bug slipped in with change set 11572_:_ ad22c711ccb7 <http://xenbits.xensource.com/xen-unstable.hg?cs=ad22c711ccb7>. This patch is essential and should get into 3.0.3. I tested the patch with security off and on. Thanks Reiner P.S. We are

Dear colleagues, Happy New Millennium, first of all! It would be very nice to be able to use indentation inside \code{ } as well, not only in \examples{ } when writing Rd-help files. Such a situation arrises, for instance, if one wishes to include a small piece of code in the _main_ text but not in the end as \examples{ } command does. The only way I know to put the next 3 lines my.function <-

On Wed, Nov 20, 2019 at 09:36:19PM +0800, Krzysztof Kozlowski wrote: > Adjust indentation from spaces to tab (+optional two spaces) as in > coding style with command like: > $ sed -e 's/^ /\t/' -i */Kconfig > > Signed-off-by: Krzysztof Kozlowski <krzk at kernel.org> Queued for 5.6 in drm-misc, thanks for your patch. -Daniel > --- >

On 28/01/11 14:14, Ken Dyck wrote: [...] > I've developed an LLVM back end for a DSP with 24-bit word-addressable > memory, basically by defining the alignment of i8 to be the word size > of the machine. So it _is_ possible. I think I might have an easier job of it, as I don't want to use any of the standard C sizes at all --- my char will be ~64 bits wide (in fact, my

>From 1da1502b33d50bc0614a20bc217876fcb8f05d39 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at vv.meyering.net.meyering.net> Date: Thu, 24 Sep 2009 09:24:55 +0200 Subject: [PATCH libguestfs] maint: use spaces, not TABs for indentation "make syntax-check" was failing. This fixes it. * HACKING: Indent with spaces, not TABs. * configure.ac: Likewise. *

this is semi-off topic but still related to ror. i had a problem with testing my depot program (which i follow the tutorial in agile web development book). it took me many hours to solved the problem. all the while i thought i was using spaces inside the test/fixtures/products.yml programmer_book: id: 1 title: Pragmatic Programmer description: Best book