search for: uncaring

Dear R-devel, The doc of exists, get and get0 is unambiguous, x should be an object given as a character string. However these accept longer inputs. It can lead an uncareful user to think these functions are vectorized when they're not, and generally lets through bugs that one might have preferred to trigger earlier failure. ``` r exists("d") #> [1] FALSE exists(c("c",

I noticed the recent commit to R-dev (r79434). Is this wise? I've often used get() in constructions like for (j in ls()) if (is.numeric(x <- get(j))) ... (and often interactively, rather than in a package) Am I to understand that get(j) will now be equivalent to `j` even if j is a string referring putatively to another object? On Sat, 14 Nov 2020 at 01:34, <luke-tierney at

Come on, folks. There is no NSE involved in calls to get(): it's standard evaluation all the way into the C code. Prior to the change a first argument that is anything other than a character vector would produce an error. After the change, passing in a symbol will do the obvious thing. Code that worked previously without error (i.e. called get() with string values) will continue to work

Worth looking into. It would probably cause some check failures, so would probably be a good idea to run a check across BIOC/CRAN. At the same time it would be worth allowing name objects (type "symbol") so thee don't have to be converted to character for the call and then back to names internally for the environment lookup. Best, luke On Fri, 13 Nov 2020, Antoine Fabri wrote:

Hi all, I have used variable values in get() as well, and including, I think, in package code (though pretty infrequently). Perhaps a character.only argument similar to library? ~G On Mon, Nov 16, 2020 at 5:31 PM Hugh Parsonage <hugh.parsonage at gmail.com> wrote: > I noticed the recent commit to R-dev (r79434). Is this wise? I've > often used get() in constructions like >

There are times when ZFS options can not be applied at the moment, i.e. changing desired mountpoints of active filesystems (or setting a mountpoint over a filesystem location that is currently not empty). Such attempts now bail out with messages like: cannot unmount ''/var/adm'': Device busy cannot mount ''/export'': directory is not empty and such. Is it

hi all My name is Kendell Clark, and I've just subscribed to this list. I thought I'd write this email to introduce myself, and ask a couple of questions about configuring samba. I'm a co developer of a linux distribution for the visually impaired and disabled called Sonar GNU linux, which you can learn more about at http://www.sonargnulinux.com. I've been struggling to come up