search for: guidelines

Displaying 20 results from an estimated 2211 matches for "guidelines".

2014 Mar 02
2
[LLVMdev] [RFC] The coding standard for "struct" should be relaxed or removed
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-PO...
2014 Mar 02
3
[LLVMdev] [RFC] The coding standard for "struct" should be relaxed or removed
On Mar 1, 2014, at 7:15 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Sat, Mar 1, 2014 at 5:59 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > 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...
2002 Feb 04
1
Guidelines for Rd-Files
Dear list, on p. 11 of "Writing R-extensions" I read "See the ``Guidelines for Rd-files'' for guidelines ... which should be useful..." Where can I find these guidelines? Best, Christian -- *********************************************************************** Christian Hennig Seminar fuer Statistik, ETH-Zentrum (LEO), CH-8092 Zuerich (current) and Fac...
2005 Sep 17
3
Mailing list guidelines and moderation
Hey Guys, I am looking to put together a set of guidelines for posting on the CentOS Mailing Lists. The aim being that we come up with a framework that is then enforceable by a moderator, should the need arise. Blanket user / thread moderation is something that I dont really want to enforce here - but might be a necessary evil, over a short period of...
2019 Feb 03
3
RFC: Modernizing our use of auto
...> My understanding is that there has been no widely understood or accepted > policy, so different coders and reviewers are doing different things. > > One of the things which has no consensus here is whether 'auto' may be > used in lambdas (using c++-14). Under the current guidelines, my understanding is that nothing prevents to use auto in lambda in order to "make the code more readable" when "the type is already obvious from the context" or "when the type would have been abstracted away anyways, often behind a container’s typedef such as std::vector&l...
2018 Dec 31
4
RFC: Modernizing our use of auto
On Dec 16, 2018, at 11:44 AM, Stephen Kelly via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 25/11/2018 14:43, Stephen Kelly via llvm-dev wrote: >> However this is a proposal for more modern thinking regarding the permissiveness of auto in LLVM codebases. >> Currently the rule on the use of auto is here: > > Hi, > > Thanks for the input on this topic,
2015 Aug 21
2
Guidelines for pass initialization?
Does anyone know what the guidelines are supposed to be for properly initializing a pass? Looking around, we seem to have three styles of pass registration in use. INITIALIZE_PASS(...) INITIALIZE_PASS_BEGIN(...) INITIALIZE_PASS_DEPENDENCY(...) ... INITIALIZE_PASS_END(...) static RegisterPass<FooPass> X(...); (This is the o...
2018 Sep 18
4
[CentOS-devel] Authorization to use CentOS logo in GNOME Boxes
...S_color_logo.svg Hi Fabiano, Thanks for clarifying and that connects with what Rich said about how we've used just the graphic logo mark in practice but do not have a guideline that allows that on the ArtWork wiki. This item is actually on my short list of things to clarify for the trademark guidelines and updates on the ArtWork page. For the moment, we can pursue a specific permission for GNOME Boxes. Can you provide a mock-up of how it would appear on the page? I'm looking at https://wiki.gnome.org/Apps/Boxes but am not sure how it would appear. Am I correct that the logo would appear wh...
2018 Oct 31
1
[CentOS-devel] Authorization to use CentOS logo in GNOME Boxes
...gt; > Hi all, > > There is now a draft permission letter working it's way through the > CentOS Board. It is intended to cover permission for just the GNOME > Project's use with GNOME Boxes. This is *really* good news! > > I am still pursuing resolving this within the guidelines, that will take > more time. What does it mean, exactly? Does it mean that a logo, as the one done for docker, will be prepared for Boxes usage meanwhile or that we'll have to solve the guidelines issues as the first thing? Thanks a lot for helping us here! > > Best regards, > &gt...
2019 Nov 18
2
Perl was: JMAP: Re: http API for IMAP
...is > weekend :) I am a big biased. AFAIK it is written in Perl. I am very happy that I did not need to use Perl since 18 years now. The regex where great. But time has changed. Everytime you use regex today, I feel like being on the wrong track. Related: https://github.com/guettli/programming-guidelines#regex-are-great---but-its-like-eating-rubbish Regards, Thomas G?ttler > Cheers, > > Bron. > > On Fri, Nov 15, 2019, at 00:44, Thomas G?ttler via dovecot wrote: >> Am 14.11.19 um 14:03 schrieb Benny Pedersen via dovecot: >> > Thomas G?ttler via dovecot skrev d...
2011 Sep 29
1
Tcl/Tk Guidelines
Hello, I wanted to ask if there are any guidelines for Tcl/Tk programming in R ? I know that there are no strict rules concerning programing. But perhabs there are some useful tipps how to organise Tcl/Tk code in your R script. I want to programm a little GUI and I don't want to reprogram the whole GUI in the middle, when I discover that I have...
2009 Jan 10
6
Guidelines for CentOS Mailing List posts
Some people don't know how to conduct themselves on usenet and mailing lists. Despite the mailing list guidelines being crystal clear about no html posting and not top-posting we have people still doing so. People still use text-readers to access the mailing list so you could be denying access to these people by flouting the mailing list guidelines. This is an example of top-posting http://lists.centos.org/...
2012 Jun 04
0
[LLVMdev] style guidelines
...one style or another. Frankly, I just don't care *what* the style is nearly as much as I care that it is consistently applied. I'll add minor points: - I suspect LLVM/Clang/... have plenty of good reasons to deviate from any existing style. We shouldn't constrain ourselves to external guidelines at this point; these are large healthy projects. - We can fix any problems or inconsistencies with the style guidelines if contributors can agree to what they are and what would be a superior alternative. Finally: They have a nice script for c++ which will check for many things. > It is not...
2012 Jun 04
2
[LLVMdev] style guidelines
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
2019 Apr 15
2
LLVM Social Guidelines
Hi folks, At EuroLLVM we had a round table for organizers of LLVM Socials around the globe. After the discussion we decided to get some sort of guidelines for those who want to organize the meetup in their city, but have any questions and don't know where to start. Currently, I am creating the very first draft. Once it's in a good shape I will send it to the phabricator. I am looking for help from other organizers and anyone who wants to co...
2019 May 10
2
LLVM Social Guidelines
...vm.org/D61550 > >> On 15. Apr 2019, at 16:01, Alex Denisov <1101.debian at gmail.com> wrote: >> >> Hi folks, >> >> At EuroLLVM we had a round table for organizers of LLVM Socials around the globe. >> After the discussion we decided to get some sort of guidelines for those who want to organize the meetup in their city, but have any questions and don't know where to start. >> >> Currently, I am creating the very first draft. Once it's in a good shape I will send it to the phabricator. >> >> I am looking for help from other o...
2018 May 24
3
Style: getFoo() vs foo()
The coding guidelines say: > Function names should be verb phrases (as they represent actions), and command-like function should be imperative. The name should be camel case, and start with a lower case letter (e.g. openFile() or isFoo()). This means that functions that just compute or access a value (no side-effect...
2017 Apr 07
2
Any interest in a patch for setting the syslog facility for the ssh client?
Darren, Thanks, evidently I need to practice my reading skills. I did some practice on the style guide, and I believe that I have the patch fixed up per the style guidelines. I've attached the new patch to this email for review. Cheers, Ethan On Fri, Apr 7, 2017 at 5:02 AM, Darren Tucker <dtucker at zip.com.au> wrote: > On Fri, Apr 7, 2017 at 4:45 PM, Ethan Rahn <ethan.rahn at gmail.com> wrote: > >> To revive this thread - I filed a bug...
2015 Mar 06
3
[LLVMdev] [cfe-dev] Commit message policy?
On 6 March 2015 at 18:33, Hal Finkel <hfinkel at anl.gov> wrote: > Hi Renato, > > Did anything ever happen with this? Nope. People didn't want to commit to limits but still have a guideline. I'm of the view that guidelines are meant to be ignored. Do you want to continue pushing this? cheers, --renato
2019 Nov 19
1
Perl was: JMAP: Re: http API for IMAP
Am 18.11.19 um 16:18 schrieb Ralph Seichter via dovecot: > * Thomas G?ttler via dovecot: > >> https://github.com/guettli/programming-guidelines#regex-are-great---but-its-like-eating-rubbish > > Thanks for including the disclaimer "It's my personal opinion and > feeling. No facts, no single truth." in your 'guidelines' (many of which > I disagree with). I just wish you had included the same disclaimer in &...