similar to: [LLVMdev] Improving cast<> failure messages.

I'm doing some chi-square tests, and I recall some arbitrary rule that says each band must have at least 5 events in order for the test to be meaningful. Is there some way to do the banding automagically in R ? For instance, in the following survdiff, I'm trying to see if ADL affects survival. But when ADL=3,5 and 6, the number observed is too little. Anyway for me to tell R how to group

This has been bugging me for years but never got around to spending a lot of time on it until I now want/need to use it for work stuff. Problem is simple I get access denied when trying to create a file in a directory that is not owned by me or my primary group that doesn't have world writable permissions. Ive also had similar issues with NFS mounts where I can't move/create/delete files

Hi, i've two papers that could be listed on the LLVM publication page. http://www.llvm.org/pubs/ The first paper describes an architecture description language and LLVM back-end generation out of an ADL. The second paper describes a cluster VLIW back-end for LLVM 2.9, just before this VLIW initiative started for LLVM. Kind regards, Timo Stripf Stripf, T.; Koenig, R.; Becker, J.; , "A

On Dec 3, 2009, at 5:24 AM, Ahmed Charles wrote: > Sorry, always end up not replying to the list: > > The main issue with dealing with next this way is that people adding new uses of next will probably not be using c++0x and therefore won't know it's ambiguous and that it needs to be qualified. True. But when this code is compiled under C++0X you get an easy to diagnose, easy

On Nov 16, 2009, at 10:49 AMPST, Howard Hinnant wrote: > On Nov 16, 2009, at 1:43 PM, Dale Johannesen wrote: > >> >> On Nov 14, 2009, at 3:16 PMPST, Howard Hinnant wrote: >> >>> In many places there is code that looks like: >>> >>> MBBI = next(MBBI); >>> >>> In C++0X there is a std::next that is likely to be in scope when

In many places there is code that looks like: MBBI = next(MBBI); In C++0X there is a std::next that is likely to be in scope when these calls are made. And due to ADL the above call becomes ambiguous: llvm::next or std::next? I recommend: MBBI = llvm::next(MBBI); -Howard

On Nov 16, 2009, at 1:43 PM, Dale Johannesen wrote: > > On Nov 14, 2009, at 3:16 PMPST, Howard Hinnant wrote: > >> In many places there is code that looks like: >> >> MBBI = next(MBBI); >> >> In C++0X there is a std::next that is likely to be in scope when these >> calls are made. And due to ADL the above call becomes ambiguous: >>

Whether can any R package run Full modified OLS (Phillips and Hansen 1990 ), DOLS (Stock and Watson 1993) and ADL model (Pesaran and Shin 2001) for cointegrated VAR model? I cannot find any useful order in VAR and SVAR package. Thanks. Eric Wang [[alternative HTML version deleted]]

Hi, I am trying to run ADL model by using auto.arima in package "forecast". I put two time series,x and xreg, in the formula, but got message: Error in nsdiffs(xx) : Non seasonal data. Any one can tell how to use it? Thanks Richard *************************************************************************************************** IMPORTANT: * This transmission is intended for the

I am pretty sure the .cpp files always explicitly use "llvm" namespace. Look for: using namespace llvm; Is that sufficient? Evan On Nov 14, 2009, at 3:16 PM, Howard Hinnant wrote: > In many places there is code that looks like: > > MBBI = next(MBBI); > > In C++0X there is a std::next that is likely to be in scope when these > calls are made. And due to ADL

Evan Cheng wrote: > I am pretty sure the .cpp files always explicitly use "llvm" namespace. Look for: > using namespace llvm; > > Is that sufficient? > No; once it's visible through ADL (because ilist<>::iterator extends std::iterator) there's no hiding or precedence mechanism we can exploit. On the other hand, AFAICT std::next is interchangeable with

On Sun, 15 Nov 2009 22:49:42 -0800, Evan Cheng <evan.cheng at apple.com> wrote: > I am pretty sure the .cpp files always explicitly use "llvm" namespace. > Look for: > using namespace llvm; > > Is that sufficient? > No. To prevent ADL from finding std::next, you need an explicitly qualified name at the call site. Sebastian

Howard Hinnant wrote: > On Nov 16, 2009, at 1:43 PM, Dale Johannesen wrote: > > >> "next" is a popular name; if it breaks llvm, I'd expect this standards change to break a lot of existing code. Do you really want to do that? >> > > I'm happy to open an LWG issue for you on this subject. Here are directions on submitting an issue: > >

Hi, Has anyone in R core thought about providing "hyper-dual numbers" in R? Hyper-dual (HD) numbers, invented by Jeffrey Fike at Stanford, are useful for computing exact second-order derivatives (e.g., Hessian). HD numbers are extensions of complex numbers. They are like "quaternions" and have 4 parts to them (one real and 3 non-real). They seem to be available in Julia.

Hola compañeros, Soy nuevo y me disculparan si la pregunta es muy básica. Quiero crear una función que me permita recibir variables que pueden ser 2, 3 o más, la idea es llamar esta función e indicarle la ruta y el nombre de las variables para luego realizar algún análisis. Mi idea es la siguiente: library(foreign) FDatos <- function(Ruta,Nombre,Variables){ Datos <-

C++ newbie question: But doesn't all the code in LLVM avoid "using namespace std"? It seems like the solution is to just never use both the llvm and std namespace in the C++ file. Reid On Mon, Nov 16, 2009 at 3:21 AM, John McCall <rjmccall at apple.com> wrote: > Evan Cheng wrote: >> I am pretty sure the .cpp files always explicitly use "llvm" namespace.

On Nov 14, 2009, at 3:16 PMPST, Howard Hinnant wrote: > In many places there is code that looks like: > > MBBI = next(MBBI); > > In C++0X there is a std::next that is likely to be in scope when these > calls are made. And due to ADL the above call becomes ambiguous: > llvm::next or std::next? > > I recommend: > > MBBI = llvm::next(MBBI); > > -Howard

Hi, Please could someone take a look at the below code and tell me where it is failing ? Facter.add(''syslocation'') do #confine :kernel => "Linux" setcode do name = Facter.value(''hostname'') case name when /^e(t|d|u|s|p|q)(p|v)(sol|lin)\d+/ "E DC" when

Hi, Nikolaos Kavvadias wrote: > Quoting Richard Pennington <rich at pennware.com>: > > I've just started looking into code generation and have a newbie > > question: Is there enough information in the .td files to make a > > tool to automatically generate an assembler from them? Is a project > > like that in the works? > > your question is reasonable,

Finally following up here... We ended up writing a JSON parser and checking it in under clangd/. We've been using that for a while now without hitting new problems. The header is here: https://reviews.llvm.org/source/clang-tools-extra/browse/clang-tools-extra/trunk/clangd/JSONExpr.h It's a DOM-based approach with objects on the heap. There's no streaming parser, though one could be