search for: unquoting

--- On Fri, 6/11/09, tlumley at u.washington.edu <tlumley at u.washington.edu> wrote: > From: tlumley at u.washington.edu <tlumley at u.washington.edu> > Subject: Re: [Rd] A fix that for 'bquote' that may work? (PR#14031) > To: suharto_anggono at yahoo.com > Cc: r-devel at stat.math.ethz.ch, R-bugs at r-project.org > Date: Friday, 6 November, 2009, 11:42 PM >

...ote" The reason that I want to do this is that I have a frame with a rather large number of variables and I would like to loop over the names and print out various descriptive summaries of the variable's distribution. OK, OK, I could just go > AF[,2] [1] 3 4 but once I thought of unquoting I have some sort of inner need to know how to do it! Cheers, Murray -- Dr Murray Jorgensen http://www.stats.waikato.ac.nz/Staff/maj.html Department of Statistics, University of Waikato, Hamilton, New Zealand Email: maj at waikato.ac.nz Fax 7 838 4155 Phone +...

Changes from v1 to v2: - split the "simple unquoting" as helper - pass the unquoting function to split_key_value_strings - use right unquoting function when applying split_key_value_strings Pino Toscano (2): daemon: add split_key_value_strings helper daemon: use split_key_value_strings daemon/inspect_fs_unix.ml | 93 +++++++++++++++++++---...

Dear R-devel, There is a new feature in R-devel, which explicitly refers to LISP @ operator for splicing. > The backquote function bquote() has a new argument splice to enable splicing a computed list of values into an expression, like ,@ in LISP's backquote. Although the most upvoted SO question asking for exactly LISP's @ functionality in R doesn't seems to be addressed by this

Changes from v2 to v3: - split_key_value_strings renamed to parse_key_value_strings Changes from v1 to v2: - split the "simple unquoting" as helper - pass the unquoting function to split_key_value_strings - use right unquoting function when applying split_key_value_strings Pino Toscano (2): daemon: add split_key_value_strings helper daemon: use parse_key_value_strings daemon/inspect_fs_unix.ml | 93 +++++++++++++++++++---...

On Mon, Oct 16, 2017 at 05:58:10PM +0200, Pino Toscano wrote: > Add a simple helper to turn a list of strings into key/value pairs, > splitting by '=', with the possibility to apply a function to unquote > values. > > Add also a simple unquote function. > --- > daemon/utils.ml | 16 ++++++++++++++++ > daemon/utils.mli | 11 +++++++++++ > 2 files changed, 27

Full_Name: Suharto Anggono Version: 2.8.1 OS: Windows Submission from: (NULL) (125.165.81.124) Sorry for repost. There is already PR#9602, but the problem is still there. There is also a post "Re: [R] using bquote to construct function" in R-help 2008-10-02. This illustrates the problem. C:\Program Files\R\R-2.8.1\bin>R --vanilla R version 2.8.1 (2008-12-22) Copyright (C) 2008

...nt). Here, @x would resolve to `mpg` and mutate would retain the duty of resolving that to mtcars$mpg as per normal. A seperate SE version would not be required (as arguments could be set programatically), but an additional flexibility could be @ acting on a string rather than an object for direct unquoting mutate(mtcars, z = @"mpg") for when the name is known but NSE isn't desired (which would also assist with the whole utils::globalVariables() vs CRAN checks concern). Having a formal argument forcefully auto-unquote would prevent standard usage unless there was a way to also dis...

(please be gentle, it's my first time) I am interested in discussions (possibly reiterating past threads -- searching didn't turn up much) on the possibility of supporting standard evaluation unquoting at the language level. This has been brought up in a recent similar thread here [1] and on Twitter [2] where I proposed the following desired (in-principle) syntax f <- function(col1, col2, new_col_name) { mtcars %>% mutate(@new_col_name = @col1 + @col2) } or closer to home...

Add a simple helper to turn a list of strings into key/value pairs, splitting by '=', with the possibility to apply a function to unquote values. Add also a simple unquote function. --- daemon/utils.ml | 16 ++++++++++++++++ daemon/utils.mli | 11 +++++++++++ 2 files changed, 27 insertions(+) diff --git a/daemon/utils.ml b/daemon/utils.ml index d87ad75db..865936280 100644 ---

...n() NULL)), splice = TRUE) #> foo(function() NULL) bquote(foo(..(quote(bar))), splice = TRUE) #> foo(bar) expr(foo(!!!function() NULL)) #> Error: Can't splice an object of type `closure` because it is not a vector. expr(foo(!!!quote(bar))) #> foo(bar) #> Warning message: #> Unquoting language objects with `!!!` is deprecated as of rlang 0.4.0. #> Please use `!!` instead. ``` We decided to disallow splicing scalars (and thus calls) in rlang even though this is a legal operation in many lisps. In lisps, the splicing operation stands for unquoting in the CDR of a pairlist. By...

On Mon, Mar 20, 2017 at 7:36 AM, Radford Neal <radford at cs.toronto.edu> wrote: > Michael Lawrence (as last in long series of posters)... > >> Yes, it would bind the language object to the environment, like an >> R-level promise (but "promise" of course refers specifically to just >> _lazy_ evaluation). >> >> For the uqs() thing, expanding calls

...here are lots of non-standard ways of doing things. Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Mar 17, 2017 at 12:14 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > William, > > Unbeknownst to me when I sent this, Jonathon Carrol started a specific > thread about unquoting and a proposal for supporting it at the language > level, which I think is a better place to discuss unquoting specifically. > That said, the basics as I understand them in the context of non-standard > evaluation, unquoting (or perhaps interpolation) is essentially substituting > part...

...off list discussions with Jonathan Carrol and with >Michael Lawrence I think it's doable, unambiguous, >and even imo pretty intuitive for an "unquote" operator. For those of us who are not CS/Lisp mavens, what is an "unquote" operator? Can you expression quoting and unquoting in R syntax and show a few examples where is is useful, intuitive, and fits in to R's functional design? In particular, what does it give us that the current tilde function does not? Bill Dunlap TIBCO Software wdunlap tibco.com On Fri, Mar 17, 2017 at 6:46 AM, Gabriel Becker <gmbecker a...

...au > <javascript:;>> > wrote: > > > (please be gentle, it's my first time) > > > > I am interested in discussions (possibly reiterating past threads -- > > searching didn't turn up much) on the possibility of supporting standard > > evaluation unquoting at the language level. This has been brought up in a > > recent similar thread here [1] and on Twitter [2] where I proposed the > > following desired (in-principle) syntax > > > > f <- function(col1, col2, new_col_name) { > > mtcars %>% mutate(@new_co...

Hi, Say I''ve got a directory full of stale Tomcat temp files of the form: /usr/local/blackboard/apps/tomcat/work/Catalina/localhost/webapps_assessment/strts6866.tmp and I want to delete any files that haven''t changed in a week and not keep any backup. Should this get rid of them: tidy {

s= "Hey" a = "Hello" table = rbind(s,a) write.table(table,paste("blah",".PROPERTIES",sep = ""),row.names = FALSE,col.names = FALSE) In my table, how do I output only the words and not the words with the quotations? -- View this message in context: http://r.789695.n4.nabble.com/How-to-unquote-string-in-R-tp3025654p3025654.html Sent from the R

...> >> wrote: >> >> > (please be gentle, it's my first time) >> > >> > I am interested in discussions (possibly reiterating past threads -- >> > searching didn't turn up much) on the possibility of supporting standard >> > evaluation unquoting at the language level. This has been brought up in >> > a >> > recent similar thread here [1] and on Twitter [2] where I proposed the >> > following desired (in-principle) syntax >> > >> > f <- function(col1, col2, new_col_name) { >> >...

...2017 at 5:03 PM, Jonathan Carroll <jono at jcarroll.com.au> wrote: > (please be gentle, it's my first time) > > I am interested in discussions (possibly reiterating past threads -- > searching didn't turn up much) on the possibility of supporting standard > evaluation unquoting at the language level. This has been brought up in a > recent similar thread here [1] and on Twitter [2] where I proposed the > following desired (in-principle) syntax > > f <- function(col1, col2, new_col_name) { > mtcars %>% mutate(@new_col_name = @col1 + @col2) &...

Michael Lawrence (as last in long series of posters)... > Yes, it would bind the language object to the environment, like an > R-level promise (but "promise" of course refers specifically to just > _lazy_ evaluation). > > For the uqs() thing, expanding calls like that is somewhat orthogonal > to NSE. It would be nice in general to be able to write something like >