similar to: Google's R Style Guide

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

On Mon, Jun 4, 2012 at 2:29 PM, reed kotler <rkotler at mips.com> wrote: > Probably this has come up before... but have we considered just adopting > the Google style guidlines and maybe modifying it in some places? > Despite working at Google, and having to cope with multiple different styles in my day-to-day work as a consequence, I would not push for this. I think that we

Ok, for what i understand, this is a compatibility issue with python 2.6. This seems to be in relation with Dict Comprehensions (https://www.python.org/dev/peps/pep-0274/). So yet, samba 4.8 cannot run on any rhel 6 like distribution. Was it intended ? Christophe Borivant ----- Mail original ----- De: "samba" <samba at lists.samba.org> À: "samba" <samba at

Hi Folks, Now that LLVM 11.0.0 has been released, it's time to prepare for the final step envisionned in the previous RFC named *[RFC] Python 2 / Python 3 status* [0], ie. requiring Python3.6 for LLVM 12.0.0, to be released in 2021. At least Fedora already only ships Python3 and we didn't have much bugs reported wrt. Python compatibility for the LLVM toolchain. Indeed, all Python scripts

I’d like to discuss revising the LLVM coding conventions to change the naming of variables to start with a lowercase letter. This should not be a discussion on the pain 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

Dear List, I'm writing to gauge interest in new syntax for positional-only function parameters to be added to R. The pattern of functions accepting other functions as inputs and passing additional ... arguments to them is prevalent throughout the R ecosystem. Currently, however, all such functions must one way or another tackle the problem of inadvertently passing arguments meant to go to

The Python language recently migrated from SVN to Mercurial as their version control system. As part of this effort, a detailed migration plan was written: http://www.python.org/dev/peps/pep-0385/ Now, I'm not proposing that we favor using Mercurial over Git*. But I would suggest that perhaps you could use the Python migration plan as a template for LLVM's migration. (*I use both

On Aug 19, 2011, at 2:36 PM, Talin wrote: > The Python language recently migrated from SVN to Mercurial as their version control system. As part of this effort, a detailed migration plan was written: > > http://www.python.org/dev/peps/pep-0385/ Hi guys, Just to be absolutely clear here, Mercurial is not being considered. -Chris -------------- next part -------------- An HTML

I understand but do you think the work will be done to make it compatible again ? If not, there should be a statement in the changelog about this broken compatibility. Christophe Borivant ----- Mail original ----- De: "Andrew Bartlett" <abartlet at samba.org> À: "Christophe BORIVANT" <cborivant at devinlec.com>, "samba" <samba at lists.samba.org>

Line 59 of samba4.0.0-alpha11/source4/utils/net.c file, at line 59 uses "Py_ssize_t", which was not defined in Python until Python 2.5. This causes havoc trying to compile it on RHEL 5, which uses Python 2.4 and which I cannot recommend upgrading the Python for in a production server environment. (I've tried that: it causes dependency hell in RHEL.) So, I suggest adding this patch

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

Thanks Bill. Do you and others think that a link to this guide (or another)should be included in the Posting Guide and/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.

This is why I posted a link to the transition plan for Python - http://www.python.org/dev/peps/pep-0385/ - to use as a model for LLVM's transition. There are a lot of questions which need to be answered: -- Where will the main repository be hosted? -- What branches will be copied over from svn to the main repository? -- What tools will be used to copy the history? -- What presubmit hooks will

I have just installed Samba 2.2.5. I am using Winbind and have changed the following in /etc/nsswitch.conf. passwd: files winbind group: files winbind I successfully joined a PDC domain. When I list files, I see that groups are being resolved from winbind. I have userid xtuser defined to Linux. I see the following: ibm9672:/home # getent passwd | grep xtuser xtuser:x:11240:11763:test

Hola: Me suena algo de que el año pasado alguien dijo algo sobre unas sugerencias de reglas de estilo para escribir código en R. No he oído nada más en esta lista (a lo mejor se me ha pasado por alto) Ayer se publicó un mensaje sobre esto precisamente en un blog en inglés: http://pairach.com/2012/06/06/r-style-guide/ (copiado debajo para facilitar la lectura y comentarios en esta lista)

Dear all I was wondering whether such a long post could be fortune-ed. What do you think? Regards Liviu On Sat, Aug 21, 2010 at 9:33 PM, Sharpie <chuck at sharpsteen.net> wrote: > Well, I can think of three ways it can go down: > > > 1. ?You want a shiny new pony. > > You ask about it on the mailing list and it seems that everyone else in the > world responds

On Tue, Jul 26, 2011 at 10:20 AM, Chris Lattner <clattner at apple.com> wrote: > > 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. > >

On Nov 29, 2012, at 12:46 PM, Eli Bendersky <eliben at google.com> wrote: > On Thu, Nov 29, 2012 at 9:41 AM, Joe Abbey <jabbey at arxan.com> wrote: >> I know this process is well documented here >> http://llvm.org/docs/GettingStarted.html >> >> But man do I love scripting things: >> >> LLVM Getting Started (See

Any updates on this? In particular, I'd like to see concrete patches proposed for review and inclusion into LLVM. I think having actual patches on the table and under review will help a great deal. Kostya, let me know if I can help prepare them. A few general comments as well inline... On Tue, Jul 26, 2011 at 1:57 AM, Kostya Serebryany <kcc at google.com> wrote: > On Tue, Jul 26,

Did the project ever come to a decision about making a transition to git? I'm trying to do some longer-term planning and it would be helpful to know what the roadmap is. Thanks! -Dave