search for: erudition

Sirs, No doubt many of the cerebral and erudite correspondents on the R-list have memorized all the functions in all the CRAN packages. But for the benefit of those less competent, such as I, could posters explicitly quote the source of non-base functions? Lately, intervals() and chron() were discussed on the list, without clear mention that they live in packages `nlme' and

Most of the questions asked in the nut-user mailing list seem to me to be either erudite technical discussion of new and exotic UPS units, or n00b questions of the style "I have this old UPS so I installed NUT but it didn't work". NUT is thoroughly documented with man pages and User Manual, but from my own experience it is not easy for Joe N00b to know what a working setup

Am 01.10.18 um 12:39 schrieb Kacper via samba: > Ok, we identified that this is a Windows bug. Is there any way to know > if and when a Windows fix will be available from Microsoft? in case an application *crahes* it's *always* the fault of that application

* zach@vmware.com (zach@vmware.com) wrote: > This code is quite dead. Release_thread is always guaranteed that the mm has > already been released, thus dead_task->mm will always be NULL. > > Signed-off-by: Zachary Amsden <zach@vmware.com> > Index: linux-2.6.13/arch/i386/kernel/process.c > =================================================================== > ---

* zach@vmware.com (zach@vmware.com) wrote: > This code is quite dead. Release_thread is always guaranteed that the mm has > already been released, thus dead_task->mm will always be NULL. > > Signed-off-by: Zachary Amsden <zach@vmware.com> > Index: linux-2.6.13/arch/i386/kernel/process.c > =================================================================== > ---

Hi Olivier, Thanks for responding! I get to learn this way. On Feb 17, 2010, at 12:50, Olivier Meurant wrote: > Hi Garrison, > > I am not a specialist of the code but here is my 2 cents: > > - I like the idea that in lazy-mode the call (in module or not) is treated by a stub (like every calls). If we go further with this, I'll have to add test cases for lazy mode. I kind

Hi, folks: I just took delivery of new PoE cables (PN 2200-11077-002) for our Polycom phones here in the office. I have the following to report, for the erudition of existing Polycom users and those considering purchasing Polycom sets from the set of models noted in the subject: 1. The cables do indeed work (hooray). 2. The cable has a module on it about a third of the way from a female end. The module is about the size and shape of a large cigarette light...

On Jun 9, 2017, at 10:16 AM, Roger Price wrote: > > Most of the questions asked in the nut-user mailing list seem to me to be either erudite technical discussion of new and exotic UPS units, or n00b questions of the style "I have this old UPS so I installed NUT but it didn't work". > > NUT is thoroughly documented with man pages and User Manual, but from my own

In thinking about this we could use a Mutex::tryacquire(...) (non-recursive), around JIT::runJITOnFunctionUnlocked(...)'s while loop, and use your JITEmitter:: getLazyFunctionStub(...) suggestion in place of forceEmitFunctionStub(...). Is the lock attempt too heavy, even if it is implemented with atomics? I'll implement this when I have time. Garrison On Feb 17, 2010, at 15:42, Garrison

Allow me to suggest a couple more sample configs: 1) Server as UPS controller with clients that are also on UPS, considering shutdown sequencing and 2) Multi power supply server with multiple UPS (with or without clients). - Tim On June 13, 2017 10:01:54 PM CDT, Charles Lepple <clepple at gmail.com> wrote: >On Jun 9, 2017, at 10:16 AM, Roger Price wrote: >> >> Most of the

Hi Garrison, I am not a specialist of the code but here is my 2 cents: - I like the idea that in lazy-mode the call (in module or not) is treated by a stub (like every calls). - If the jit is in non-lazy mode, I'm not really fan of the "stub" solution. Is it not possible to use the same mechanism as it already exists : add the function to pending list and emit it after the current

Hi all, I have two questions. Can some one give some help? The first question is regarding the pair of operators "&" and "&&". What is the difference between the two? The second question is regarding "<-" and "=". Usually we use "<-" as the assignment operator. I saw some people use "=". Is there any

The patch I recently attached to bug 2606, reproduced here, is my first attempt to solve this issue as represented by the attached test cases. To solve the foreign Module GlobalVariable problem, I modified JIT::getOrEmitGlobalVariable(...) to directly attempt to map a found "external" GlobalVariable. To solve the foreign Module Function problem, I modified both JIT.{h,cpp} and

Sorry i had a misprint in the appendix code in the last email Hi I needed some help with ANOVA I have a problem with My ANOVA analysis. I have a dataset with a known ANOVA p-value, however I can not seem to re-create it in R. I have created a list (zzzanova) which contains 1)Intensity Values 2)Group Number (6 Different Groups) 3)Sample Number (54 different samples) this is created by the