search for: puritan

...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...

...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...

...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...

...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...

...... 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 "...

...en you should learn the command syntax of every command that you are called upon to use. This is the one-and-only path to enlightenment. Like upholding motherhood and promoting the wholesomeness of apple-pie this sort of moralizing really brooks no answer. You can guess my opinion on that line of puritanism. As you have painfully discovered, infrequently used utilities and commands are difficult to deal with. The process of learning, or relearning, the correct arcana is particularly noisome given the notorious inconsistency of syntaxes across different utilities and the spotty coverage of up-to-d...

...; > 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 u...

...>> 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-fallt...

...ommand syntax of > every command that you are called upon to use. This is the > one-and-only path to enlightenment. Like upholding motherhood and > promoting the wholesomeness of apple-pie this sort of moralizing > really brooks no answer. You can guess my opinion on that line of > puritanism. HA! You only really need to learn *one* command: the man command. The man provides 'enlightenment' for all other commands: man vgdisplay man lvdisplay man lvcreate man lvextend man lvresize man lvreduce man lvremove man e2fsck man resize2fs These are the only LVM commands I use re...

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

...vetica, sans-serif" size=3D"2"><str= ong>Bui<altimeter>ld Mus<maestro>cle To<bimetallism>ne</strong></= font></li> <li><font face=3D"Verdana, Arial, Helvetica, sans-serif" size=3D"2"><str= ong>Rev<puritan>erse Agi<vertebral>ng</strong></font></li> <li><font face=3D"Verdana, Arial, Helvetica, sans-serif" size=3D"2"><str= ong>Inc<ashtray>rease Ene<prim>rgy</strong></font></li> <li><font face=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

...7424 Path of Exile: Graphical Glitches with GLSL Disabled 37596 Sketchup 2015 fails on unimplemented function SHELL32.dll.SHAssocEnumHandlers 37635 Explicit environment variables passed to spawn/exec are corrupted 37653 valgrind shows a definite leak in comctl32/tests/imagelist.c 37679 Puritan Hard Drive (PHD) KnowledgeBase Demo crashes on startup 37690 Propellerhead Reason 8 needs kernel32.GetUserPreferredUILanguages 37695 joySetCapture fails with uPeriod==0 37704 K-Lite installer complains about regsvr32 version being wrong ----------------------------------------------------...

...nding a cert in /etc/puppet/ssl/certs, but I don''t see it looking for any requests at all. > I''m going to download a source version of the latest stable version > and see if this makes a difference. I can''t imagine it will; certs have been stable for ages. -- Puritanism: The haunting fear that someone, somewhere, may be happy. -- H. L. Mencken --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com ------------------------------ Message: 4 Date: Sat, 13 Oct 2007 12:58:1...