search for: sprinkle

In a lattice 11x11 with 6 repetitions, we want to compare lines to their two parents. 3 of the 6 repetitions are sprinkled and the 3 others not. There are 5 factors : hm (hydrous mode), variety, block, rep and grandrep. grandrep gathers two repetition, a sprinkled and a not (as in Split Plot !). I use lme but I have problems in random. Can someone help me ? Ibnou DIENG --------------------------------- [[al...

Sprinkling my examples with ''lambda'' has always seemed like a bit of a wart to me. I''ve gotten into the habit of adding ''alias :calling :lambda'' to my spec suites. My examples then look like: calling { Foo }.should raise_error calling { Bar }.should_not raise_error Is there a reason that RSpec core has chosen not to make exception expectations more

...well, there is a fundamental limitation there, not an issue with CMake. Autoconf has a hack for building LLVM as a single, monolithic dll while using MinGW. That hack can be easily replicated on CMake. As for Visual Studio, autoconf is pretty useless, so no dll's there in any case until someone sprinkles the LLVM C++ sources with the necessary declarations. > it can hardly be said to support all use cases!

Hey all. This morning I found that my audio playback is randomly sprinkled with sound skips and dropouts. I went to /var/log/yum.log and found this: Feb 09 20:18:22 Updated: lame-3.99.4-2.el6.rf.i686 I'm not saying that caused the problem but it's all I could find that changed. When I ls in /dev there is no dsp entry. That would explain why mplayer Can'...

I have a Grandstream GSX-2000 with .. Software Version: Program-- 1.0.0.3 Bootloader-- 1.0.0.3 I tried to do an HTTP update from the Grand Stream web site... After half an hour, I recycled power and now its dead... LED's come on and stay on, screen and buttons are dead. Connectivity to Grandstream.com was always good - whenever I checked (I downloaded the "User Manual" in a

...unch of data into those tables from existing models. It works great. As expected. Tables are created. Relationships are made. Everything comes out fine as far as the data goes. But for some reason the migration task ends with this error: rake aborted! negative argument I''ve liberally sprinkled my migration with "say" commands so I can see where this happens, and it happens at the end of the migration after everything the migration is actually doing has finished. Any clues? Thanks for any help. -------------- next part -------------- An HTML attachment was scrubbed... URL: h...

This is a best practices / style question. The way I use RODBC is I something like this: > foo <- sqlQuery(db, "select * from foo") > apply(foo, 1, function{...}) That is, I use apply to iterate over each result -- row -- in the RODBC-produced dataframe. Is this how one generally wants to do this? My concern is that when apply iterates over the rows, it uses as.matrix()

...be warning in cases where it would actually cause a problem (i.e., misspelled options or specifying options that conflict). Conflicting options _should_ already be handled. Detecting unknown or misspelled options is very straight forward to implement which doesn't require claim() calls to be sprinkled throughout the driver. Mostly I'm looking for counter arguments as to why this warning should remain given the heavy burden.. Chad

...ontentType" added. SHN_ABS symbols can have different types, STT_OBJECT, STT_FILE and maybe others. In order for the writer to tell it must have a way to reach back and ask the atom what type of symbols caused it to be created. To that end I added a contentType method to AbsoluteAtom and sprinkled changes around to make this work. What do the V1 suffixes mean in the Native code? I had to add a new Attributes array to for the Absolute atoms and simply used, NCS_AttributesArrayV2 following the lead of NCS_ReferencesArrayV[12] -- Qualcomm Innovation Center, Inc. is a member of Code Auro...

Dear R Wizards---is it possible to get R to show its current call stack (sys.calls()) upon an error abort? I don't use ESS for execution, and it is often not obvious how to locate how I triggered an error in an R internal function. Seeing the call stack would make this easier. (right now, I sprinkle "cat" statements everywhere, just to locate the line where the error appears.) Of course, I would really love to see the line in my program that triggered this, but I have asked this before, and I understand this is too difficult to get into the R language. regards, /iaw ---- Ivo Welc...

...hat we can have scheduled MachineInstructions living alongside DAGs in such a way that changing the DAG (adding/removing a couple of instructions, say) doesn't _necessarily_ require rescheduling the whole function. I'm thinking of a future JIT here, where it would be nice to be able to sprinkle/reap instrumentation code over functions at high speed. Duraid

On Mon, 13 Nov 2017 15:20:05 +0100 Sven Schwedas <sven.schwedas at tao.at> wrote: > > > PS, your configs are still wrong. > > It would be *really* helpful if you explained *why*. Sprinkling magic > pixie dust over random config files isn't exactly purposeful > debugging. > Lets start with /etc/krb5.conf Samba doesn't need most of what you will find in it,

On Fri, Apr 6, 2012 at 6:15 PM, Alan Garny <agarny at hellix.com> wrote: > Hi, > > From what I have seen on this mailing list and elsewhere, it would seem that > it isn’t possible to build LLVM as a shared library using Visual C++. Still, > I would imagine that quite a few people are or would be interested in it, > so… is there any plan to support this any time soon? This,

...ng them to 0 just because we are > > using the new VMW_PORT here. Why do we need to switch? What is the > > benefit of doing this? > > There are two reasons. One is to make the code more readable and > maintainable. Rather than having mostly similar inline assembly > code sprinkled across multiple modules, we can just use the macros > and document that. But the macro is only used here, and the variables aren't used at all, so it makes no sense in this file. > The second reason is this organization makes some on-going future > development easier. We don't...

...ng them to 0 just because we are > > using the new VMW_PORT here. Why do we need to switch? What is the > > benefit of doing this? > > There are two reasons. One is to make the code more readable and > maintainable. Rather than having mostly similar inline assembly > code sprinkled across multiple modules, we can just use the macros > and document that. But the macro is only used here, and the variables aren't used at all, so it makes no sense in this file. > The second reason is this organization makes some on-going future > development easier. We don't...

...t to 1024 which > + * should be more than enough for real use cases. Note that the actual > + * limitation comes from the display mode: > + * hborder < hdisplay && vborder < vdisplay > + */ > + drm_connector_attach_underscan_properties(connector, We should probably sprinkle __must_check over all these :-) -Daniel > + BIT(DRM_UNDERSCAN_OFF) | > + BIT(DRM_UNDERSCAN_ON), > + 1024, 1024); > + > connector->polled = (DRM_CONNECTOR_POLL_CONNECT | > DRM_CONNECTOR_POLL_DISCONNECT); > > @@ -408,6 +418,9 @@ static voi...

On Jul 26, 2012, at 4:07 PM, Chris Lattner <clattner at apple.com> wrote: > <dropping llvm-commits> > > On Jul 2, 2012, at 9:59 AM, Alexander Kornienko wrote: > >> Hi llvmdev, llvm-commits, >> >> There was a discussion on this topic a while ago, and now I've decided to make a formal proposal and post it here. > > I missed the earlier

Hi all, The "ls" function wears two hats. It allows users to inspect an environment interactively and also serves deeper in code as the accessor for an environment's names/keys. I propose that we separate these two conflicting goals, keeping ls for interactive use and adding names for a quick listing of the hash keys. This involves adding two lines to do_names in attrib.c. The

...fundamental limitation >there, not an issue with CMake. Autoconf has a hack for building LLVM as >a single, monolithic dll while using MinGW. That hack can be easily >replicated on CMake. As for Visual Studio, autoconf is pretty useless, >so no dll's there in any case until someone sprinkles the LLVM C++ >sources with the necessary declarations. So the problem's not with the build system, it's that the source code itself is just not written right and it only builds under other systems by exploiting some weird hack? Thanks, that's good to know.  C/C++ really isn't...

>From: Óscar Fuentes <ofv at wanadoo.es> >Subject: Re: [LLVMdev] [cfe-dev] is configure+make dead yet? > >As for Visual Studio, autoconf is pretty useless, >so no dll's there in any case until someone sprinkles the LLVM C++ >sources with the necessary declarations. Thinking about this a little more, is that even necessary?  Exporting the C++ API in a DLL is useless due to name mangling and probably memory management issues as well.  The only thing that should really need to be marked as exported is...