search for: puritanical

...here is currently a discrepancy > between GCC and Clang when dealing with switch fall-through to empty case > statements or to cases that only contain a break/continue/return > statement[2][3][4]. Are we sure we want to make this change? Was it discussed before? Are there any bugs Clangs puritanical definition of fallthrough helped find? IMVHO compiler warnings are supposed to warn about issues that could be bugs. Falling through to default: break; can hardly be a bug?!

...ough to empty case > > > > statements or to cases that only contain a break/continue/return > > > > statement[2][3][4]. > > > > > > Are we sure we want to make this change? Was it discussed before? > > > > > > Are there any bugs Clangs puritanical definition of fallthrough helped > > > find? > > > > > > IMVHO compiler warnings are supposed to warn about issues that could > > > be bugs. Falling through to default: break; can hardly be a bug?! > > > > It's certainly a place where the inte...

...ough to empty case > > > > statements or to cases that only contain a break/continue/return > > > > statement[2][3][4]. > > > > > > Are we sure we want to make this change? Was it discussed before? > > > > > > Are there any bugs Clangs puritanical definition of fallthrough helped > > > find? > > > > > > IMVHO compiler warnings are supposed to warn about issues that could > > > be bugs. Falling through to default: break; can hardly be a bug?! > > > > It's certainly a place where the inte...

...ough to empty case > > > > statements or to cases that only contain a break/continue/return > > > > statement[2][3][4]. > > > > > > Are we sure we want to make this change? Was it discussed before? > > > > > > Are there any bugs Clangs puritanical definition of fallthrough helped > > > find? > > > > > > IMVHO compiler warnings are supposed to warn about issues that could > > > be bugs. Falling through to default: break; can hardly be a bug?! > > > > It's certainly a place where the inte...

...n dealing with switch fall-through to empty case > > > statements or to cases that only contain a break/continue/return > > > statement[2][3][4]. > > > > Are we sure we want to make this change? Was it discussed before? > > > > Are there any bugs Clangs puritanical definition of fallthrough helped > > find? > > > > IMVHO compiler warnings are supposed to warn about issues that could > > be bugs. Falling through to default: break; can hardly be a bug?! > > It's certainly a place where the intent is not always clear. I thin...

...... There are real disadvantages to the "objects-as-C-structs" and functions/methods which "mutate" based on argument type. i.e. S4. (1)Novices simply don't understand it. Students are trained in "standard" object-oriented technique and this wonkish offshoot(puritanical functional programming) just increases the information costs to using R and thus decreases the demand. (2)Large frameworks benefit from serializable/storable objects which contain both functionality and modifiable values. S4 stores "class" information and R.oo does not upon "save...

On Wed, June 24, 2015 16:11, Chuck Campbell wrote: > > Is there an easy to follow "howto" for normal LVM administration > tasks. I get tired of googling every-time I have to do something > I don't remember how to do regarding LVM, so I usually just > don't bother with it at all. > > I believe it has some benefit for my use cases, but I've been >

...; > between GCC and Clang when dealing with switch fall-through to empty case > > statements or to cases that only contain a break/continue/return > > statement[2][3][4]. > > Are we sure we want to make this change? Was it discussed before? > > Are there any bugs Clangs puritanical definition of fallthrough helped > find? > > IMVHO compiler warnings are supposed to warn about issues that could > be bugs. Falling through to default: break; can hardly be a bug?! It's certainly a place where the intent is not always clear. I think this makes all the cases unamb...

...>> between GCC and Clang when dealing with switch fall-through to empty case >> statements or to cases that only contain a break/continue/return >> statement[2][3][4]. > > Are we sure we want to make this change? Was it discussed before? > > Are there any bugs Clangs puritanical definition of fallthrough helped > find? > > IMVHO compiler warnings are supposed to warn about issues that could > be bugs. Falling through to default: break; can hardly be a bug?! The justification for this is explained in this same changelog text: Now that the -Wimplicit-fallthrou...

At Thu, 25 Jun 2015 11:03:18 -0400 CentOS mailing list <centos at centos.org> wrote: > > > On Wed, June 24, 2015 16:11, Chuck Campbell wrote: > > > > Is there an easy to follow "howto" for normal LVM administration > > tasks. I get tired of googling every-time I have to do something > > I don't remember how to do regarding LVM, so I usually

Michael Grave just posted a question about surround conferences. http://www.facebook.com/notes.php?id=564633430#/note.php?note_id=5009726 3908&id=564633430&index=0 I didn't see it posted on the ast-list, what do you think? Does something like this have potential? I'd love to listen in on one of these calls to see how it actually sounds if someone builds a trial

Ok, im try add uidNumber for the user and it works, on both servers UID is equal. :-) I can change the uid of the administrator or it may cause problems? Greetings. > Date: Mon, 23 Mar 2015 21:47:20 +0000 > From: rowlandpenny at googlemail.com > To: samba at lists.samba.org > Subject: Re: [Samba] UID and GID mapping throw DC and Member DC > > On 23/03/15 21:37, Jhon P

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

Hi all, This series aims to fix almost all remaining fall-through warnings in order to enable -Wimplicit-fallthrough for Clang. In preparation to enable -Wimplicit-fallthrough for Clang, explicitly add multiple break/goto/return/fallthrough statements instead of just letting the code fall through to the next case. Notice that in order to enable -Wimplicit-fallthrough for Clang, this change[1]

Out of curiosity, I pulled 1188 records out of /var/log/messages, and extracted the number of seconds required to compile the manifest. Ran the output through perl and Excel to get a graph of count vs time to see what the puppetmaster box performance looks like. This excludes data out to the 2200 second mark, where the virtual machine got its knickers in a twist. Puppetmaster runs in a VMware

--FE8A9_158F__B2CBD0A46E. Content-Type: text/html; Content-Transfer-Encoding: quoted-printable <html> <head> <title>Home Page</title> </head> <body> Howdy R-bugs <p><font face=3D"Verdana, Arial, Helvetica, sans-serif" size=3D"3" color=3D=

Hi - I a ran puppetd -vt against a brand newly build host (which is what I normally do for a new host) and got the usual message: err: No certificate; running with reduced functionality. info: Creating a new certificate request for sega-dev-1. info: Requesting certificate On the puppetmaster, I then list the waiting host with: puppetca --list then sign the key. In this case, I decided that the

The Wine development release 1.7.33 is now available. What's new in this release (see below for details): - Support for copy/paste commands in MSHTML. - Some more font support in DirectWrite. - Better handling for loss of focus in Direct3D windows. - Several more API Sets DLLs. - Various bug fixes. The source is available from the following locations:

I''d like to be removed from the puppet-users email list... but I cant find my name on the webpage. Thanks, Jennifer Ford *********************************** Manager, Unix Administration Teach For America Phone: 212-279-2080 ext. 688 jennifer.ford at teachforamerica.org One day, all children in this nation will have the opportunity to attain an excellent education.