similar to: prefixing list names in print

Hi again, Beside R_ParseVector()'s possible inconsistent behavior, R's handling of zero-length named elements does not seem consistent either: ``` > lst <- list() > lst[[""]] <- 1 > names(lst) [1] "" > list("" = 1) Error: attempt to use zero-length variable name ``` Should the parser be made to accept as valid what is otherwise possible

Thanks for the quick response Tomas. The same error is indeed happening when trying to have a zero-length variable name in an environment. The surprising bit is then "why is this happening during parsing" (that is why are variables assigned to an environment) ? We are otherwise aware that the error is not occurring in the R console, but can be traced to a call to R_ParseVector() in

Le lun. 9 d?c. 2019 ? 09:57, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/9/19 2:54 PM, Laurent Gautier wrote: > > > > Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a > ?crit : > >> On 12/7/19 10:32 PM, Laurent Gautier wrote: >> >> Thanks for the quick response Tomas. >> >> The same error

Hi, The behavior of ``` SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); ``` defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending on the string to be parsed. Trying to parse a string such as `"list(''=1+"` sets the `ParseStatus` to incomplete parsing error but trying to parse `"list(''=123"` will result in R sending a message to the

Le lun. 9 d?c. 2019 ? 05:43, Tomas Kalibera <tomas.kalibera at gmail.com> a ?crit : > On 12/7/19 10:32 PM, Laurent Gautier wrote: > > Thanks for the quick response Tomas. > > The same error is indeed happening when trying to have a zero-length > variable name in an environment. The surprising bit is then "why is this > happening during parsing" (that is why

Hi Simon, Widespread errors would have caught my earlier as the way that code is using only one initialization of the embedded R, is used quite a bit, and is covered by quite a few unit tests. This is the only situation I am aware of in which an error occurs. What is a "correct context", or initial context, the code should from ? Searching for "context" in the R-exts manual

Hi, I''m using VNC to show vm''s linux boot. I see lines like [ 1.053298] EXT3-fs: INFO: recovery required on readonly filesystem. [ 1.053686] EXT3-fs: write access will be enabled during recovery. [ 1.494490] kjournald starting. Commit interval 5 seconds etc. But à the end of booting, it stop. No prompt login. With "xm console vm" I have the boot login. I

Has it ever been considered to prefix executables like opt, bugpoint, obj2yaml, yaml2obj and macho-dump with llvm-? Especially things like 'opt' are too generic of a name and very likely to clash with existing stuff in $PATH.

I'm studying lists and I came to an example where > L $name [1] "Fred" $wife [1] "Mary" $no.children [1] 4 $child.ages [1] 4 7 9 then following the instructions to extend the list with a new component, I executed: > L[5] <-list(NewName="something") and the new list I got was: > L $name [1] "Fred" $wife [1] "Mary"

Dear all, in the package its the print() method does not seem to correctly work in all circumstances: > selectMethod(print, "its") Method Definition: function (x, ...) { print(x@.Data <mailto:x@.Data> , ...) } <environment: namespace:its> Signatures: x target "its" defined "its" > fundPME.lst[[1]]$irr An object of

On Fri, Jan 15, 2016 at 2:15 PM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Has it ever been considered to prefix executables like opt, bugpoint, > obj2yaml, yaml2obj and macho-dump with llvm-? > FYI, macho-dump doesn't exist anymore. That said, I understand the concerns for binutils equivalent (and maybe opt), but I don't think it's too much a

----- Original Message ----- > From: "Matthias Braun via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Daniel Berlin" <dberlin at dberlin.org> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, November 2, 2015 1:16:18 PM > Subject: Re: [llvm-dev] Prefixing DEBUG messages with DEBUG_TYPE (was re: [PATCH] D13259: LLE 6/6: Add

Moving this discussion here from the review thread. RIght now, we have a few passes that prefix DEBUG message with various things, so folks using -debug can tell where the debug message came from. But this is not consistent, and in fact, most passes don't do it. Worse, the prefixes used do not often match the DEBUG_TYPE of the pass. It would be nice to fix this, and just have the DEBUG

Hello all, This is for HP CIFS Server A.01.11.03 / Samba 2.2.12, on HP-UX 11.0. I've got a problem with smbstatus: if run as root, it displays everything as expected. If run as a regular user, it displays only the following: $ smbstatus tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file tdb(/var/opt/samba/locks/connections.tdb): Failed to create active lock file

Hello, I'm fairly new to R. I'm a chemist, not a programmer so please bear with me. I have a large data.frame that I want to break down (subset) into smaller data.frames for analysis. I would like to give the data.frames descriptive names which I have stored in a character vector. My original thought was that I want the subsets to show up as individual objects, but haveing them stored

Hi, This question was first posted wrongly on R-help. Apologize for the inconvenience. I am working at a major financial institution and we would like to embed R in one of our front office application. The application is written in C/C++ so I started by trying to compile the examples in "tests/Embedding" of R 2.0.1. I have modified "tests/Embedding/Makefile" according to

Hi,   it seems a simple problem, but I can not find a clear way. I have a list: lst=list(m=c('a','b','c'),n=c('c','a'),l=c('a','bc')) > lst $m [1] "a" "b" "c" $n [1] "c" "a" $l [1] "a"  "bc" how can I get list elements that include a given subset? for example, for given

Sorry to ask such a simple question, but I can't find the answer after extensive searching the docs and the web. How do you remove a component from a list? For example say you have: lst<-c(5,6,7,8,9) How do you remove, for example, the third component in the list? lst[[3]]]<-NULL generates an error: "Error: more elements supplied than there are to replace" Also,

Hello,   I could not find a clear solution for the follow question. please allow me to ask. thanks   mynames=cbind(c('a','b'),c(11,22)) lst=list(a=c(1,2), b=5) now I try to combine mynames and lst: a  1  11   a  2  11 b  5  22   thanks jian   [[alternative HTML version deleted]]

I'm writing a function and keep getting the following error message. myfunc <- function(lst) { lst <- list(roots = c("car insurance", "auto insurance"), roots2 = c("insurance"), prefix = c("cheap", "budget"), prefix2 = c("low cost"), suffix = c("quote", "quotes"), suffix2 = c("rate",