search for: _many_

Dear R-help, I first thought that the empty set (for a vector) would be NULL. x <- c() x However, the documentation seems to make clear that there _many_ empty sets depending on the vector's mode, namely, numeric(0), character(0), logical(0), etc. This is borne out by y <- letters[1:3] z <- letters[4:6] intersect(y,z) which, of course, is non-NULL: is.null(character(0)) # FALSE So, how can we test if a vector is, say, character(0)?...

...I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options...

...check xps_1.29.2.tar.gz > | now leaves only '.BBSoptions' as hidden file. > > No, still wrong. As Simon said, we all are supposed to use 'R CMD build xps' > to create the tarball. "Back in the day ..." straight tar cfz ... worked, it > more or less stopped _many_ years ago. Cf TheOneManualThatMatters: > > 1.3.1 Checking packages > ----------------------- > > Using 'R CMD check', the R package checker, one can test whether > _source_ R packages work correctly. It can be run on one or more > directories, or c...

Hello, I tried a few months ago to use IMAP with Asterisk; I used either 1.4 or the latest SVN at that time (sorry, don't remember). After a day I had to remove it since Asterisk crashed, mostly in the IMAP client code (the code of UW IMAP). My users wants IMAP back (they loved it) but not in the price of crash... I could not reproduce the crashes at the lab. They only occour on the

...eboot > The processes started at each runlevel will differ, of course. > Not all machines will run httpd on run levels 2, 3 and 5. But > none should run it at run levels 0, 1 or 6. This are the Fedora-based distro run-levels. Level 2-5 actually _differ_ on many UNIX/Linux platforms. E.g., _many_ use 3 _not_ 5 for X11. The only consistency seems to be 0, 1 and 6 -- although many distros differ on a "maintanence" run-level between 0 and 1. -- Bryan J. Smith mailto:b.j.smith at ieee.org

...[ 5> _FwdIt=llvm::TargetAlignElem *, 5> T=llvm::TargetAlignElem, 5> _InIt=llvm::TargetAlignElem * 5> ] The project would appear to have the right pre-processor definitions to suppress such warnings, but they still occur. The compiler issues _many_ warnings about conversions between uint64_t and uint, which seems to be a very common occurance. Is there any point in LLVM to having such conversions present implicitly vs explicitly (suppressing the warnings?) other than syntactic clarity? Cheers, George Russell -------------- next part --------...

...I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options...

I'm not seeing how to plot the quantities associated with two values of a factor by reading the ?xyplot help page and Deepayan's book. Perhaps I need to generate many different subsets from the data frame, but that would require _many_ new data frames. The structure of the data frame (for a single stream) has sites (factor), a date (as.Date), parameters (factor), and quantities (numeric). What I need to do is produce scatter plots of the quantities associated with two different parameters conditioned by site or by date (separ...

...I would like to propose a fairly significant change to the unused argument warning (i.e., removing it for the most part), but wanted to get some feedback before investing a great deal of time. In my opinion, the implementation of this warning is overly burdensome to maintain. Worse yet, there are _many_ cases where the driver intentionally claims unused arguments to prevent this warning from being too verbose (e.g., clang -E -g t.c -o t.i); when linking the driver claims all CompileOnly arguments. We should only be warning in cases where it would actually cause a problem (i.e., misspelled options...

...ers, irrelevant to the merge) B with columns Time and Name (and many others, irrelevant to the merge) I want the dataset AB with all these columns Open from A - a difftime (time of day) Time from B - a difftime (time of day) Name (same in A & B) - a factor, does NOT index rows, i.e., there are _many_ rows in both A & B with the same Name. all the other columns from A & B. Each row in AB must come from exactly one row in A. (i.e., dim(AB)[1] == dim(A)[1]). For each row in AB, Open>=Time, and "as small as possible". The above conditions uniquely define AB. The "obvio...

The -pre2 version of HDT 0.3.6 is out. Gert was a great source of motivation for making that -pre2. He found many bugs and gave nice ideas. Thanks Gert for your time and your _many_ tests. This release will be more or less what will be included in the incoming syslinux 3.84. Since -pre1, here come the Changelog * Reporting CPU L1 & L2 cache * Report "Hw.Virt" in cpu detection if the cpu supports vmx or svm * Fixing memory detection under the cl...

The -pre2 version of HDT 0.3.6 is out. Gert was a great source of motivation for making that -pre2. He found many bugs and gave nice ideas. Thanks Gert for your time and your _many_ tests. This release will be more or less what will be included in the incoming syslinux 3.84. Since -pre1, here come the Changelog * Reporting CPU L1 & L2 cache * Report "Hw.Virt" in cpu detection if the cpu supports vmx or svm * Fixing memory detection under the cl...

...Sat, Dec 25, 2010 at 1:18 PM, dave george <dgeorge at teletoneinc.com> wrote: > > Need some advise or paid help on running asterisk on two WAN connection. ?I > > need load balancing and failover support. > > > > WAN: 1 DSL + 1 Cable ISP. > > > > There are _many_ issues. First outgoing and incoming traffic is > completely different for what you want to do. > > Second SIP is hard enough to NAT and route with a single IP let alone > 2 or more and probably dynamic! > > Third, load balancing/fail-over is not a simple matter even doing by &gt...

...outines written in other languages. This means that (even if LLVM should be extended to support these operations eventually) you can always write them in assembly or whatever, then call them from LLVM. Note however that LLVM is _not_ a high-level language, and in fact we do not explicitly support _many_ features of HLLs directly in LLVM. We use a strategy of representing the key components of the high-level ideas using low-level primitives that can be used for a variety of purposes. If you describe what the time/sync operations are, maybe I can sketch out a suggested mapping for you. -Chris --...

hi, In high level languge there are usually have time and sync instruction, to handle async and sync operation. I want to know how LLVM take an count of these. thanks yueqiang 2003/12/19 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20031218/07381085/attachment.html>

...lib.loc, character.only = TRUE, > | > logical.return = TRUE, : > | > there is no package called 'interflex' > | > 9: In pacman::p_load("interflex") : Failed to install/load: > | > interflex > > There is a saying that you try to walk before you run. _Many_ of those > packages failing to install from source (== harder, you need dependencies, > and also slower) are in fact available as r-cran-xyz package for > Debian. Try 'apt-cache search r-cran-xyz' for different values of xyz. > > Cheers, Dirk > > -- > dirk.eddelbuett...

...b.loc, character.only = TRUE, | | > logical.return = TRUE, : | | >? there is no package called 'interflex' | | > 9: In pacman::p_load("interflex") : Failed to install/load: | | >? interflex | | There is a saying that you try to walk before you run. _Many_ of those | packages failing to install from source (== harder, you need dependencies, | and also slower) are in fact available as r-cran-xyz package for | Debian. Try 'apt-cache search r-cran-xyz' for different values of xyz. | | Cheers, Dirk | | -- | dirk.eddelbue...

...uot; list and with this product, the overwhelming objective by those that have a clue is to _not_ share the intricacies of how to accomplish basic telephony functions. Most of us do understand why a couple of cookie-Krums (intended) are scattered around though!!! There has been several attempts by _many_ to help document the product, but even _that_ effort has been consistently undermined by a select _few_. Until knowledge and experiences are shared <openly>, the product will likely remain in its present state. (Sorry Mark!) For those that have actually read this far, please express your...

Dear Simon, Thank you very much for your help, it did solve my problems!! Great! I have googled COPYFILE_DISABLE and found the following site which does explain the issue with tar on Mac OS X, see: http://unix.stackexchange.com/questions/9665/create-tar-archive-of-a-directory-except-for-hidden-files Instead of doing: $tar czf xps_1.29.2.tar.gz xps I did now: $COPYFILE_DISABLE=1 tar czf

...operator, not a bully-boss to the operator and the > authors/maintainers of every package Joe Operator might > have on his system. Actually, SELinux _is_ a "bully-boss" to the operator. It will _always_ be a "bully-boss" to the operator. > No, it doesn't. I think _many_ people other than myself have seen _many_ viewpoints on this issue. Why many people seem to think that there must be no less than an absolutism on SELinux until it accomplishes no less than the _impossible_ is beyond me. > It's about ownership of control. Is this RedHats' system >...