Displaying 17 results from an estimated 17 matches for "eq_assign".
2018 Jul 30
2
Problem with parseData
...10, 12, 11, 13, 14)"
[6] "parseData = c(0, 3, 7, 7, 5, 7, 12, 0, 0, 14, 0)"
[7] "parseData = c(\"expr\", \"SYMBOL\", \"expr\", \"LEFT_ASSIGN\",
\"NUM_CONST\", \"expr\", \"SYMBOL\", \"expr\", \"EQ_ASSIGN\",
\"NUM_CONST\", \"expr\")"
[8] "parseData = c(FALSE, TRUE, FALSE, TRUE, TRUE, FALSE, TRUE, FALSE,
TRUE, TRUE, FALSE)"
[9] "parseData = c(\"y <- 5\", \"y\", \"y\", \"<-\", \"5\", \"5\",...
2009 Nov 25
1
Question R's parser : - parsing "x=\n 1"
...rror { YYABORT; }
;
So this should be of the 3rd form.
Also, the expr_or_assign is of the 2nd form in
expr_or_assign : expr { $$ = $1; }
| equal_assign { $$ = $1; }
;
where equal_assign is
equal_assign : expr EQ_ASSIGN expr_or_assign { $$ =
xxbinary($2,$1,$3); }
When the parser sees 'x' and '=' it expects an expr_or_assign and we
know it will receive an expr. However, the expr cannot be a new
line(according to the defn of expr)
So instead of an expr, the parse gets a newline and sho...
2018 Oct 02
1
Problem with parseData
...>> [6] "parseData = c(0, 3, 7, 7, 5, 7, 12, 0, 0, 14, 0)"
>> [7] "parseData = c(\"expr\", \"SYMBOL\", \"expr\", \"LEFT_ASSIGN\",
>> \"NUM_CONST\", \"expr\", \"SYMBOL\", \"expr\", \"EQ_ASSIGN\",
>> \"NUM_CONST\", \"expr\")"
>> [8] "parseData = c(FALSE, TRUE, FALSE, TRUE, TRUE, FALSE, TRUE, FALSE,
>> TRUE, TRUE, FALSE)"
>> [9] "parseData = c(\"y <- 5\", \"y\", \"y\", \"<-\",...
2023 Nov 11
1
New syntax for positional-only function parameters?
6 ?????? 2023 ?. 22:54:24 GMT+03:00, mikkmart via R-devel <r-devel at r-project.org> ?????:
>The pattern of functions accepting other functions as inputs and
>passing additional ... arguments to them is prevalent throughout
>the R ecosystem. Currently, however, all such functions must one
>way or another tackle the problem of inadvertently passing arguments
>meant to go to
2023 Mar 11
1
Multiple Assignment built into the R Interpreter?
...nflicts) and
> its semantics (including the corner cases, some of which you have
> already mentioned). I'm not sure I'm up to the task.
>
If I were doing it, here's what I'd propose:
'[' formlist ']' LEFT_ASSIGN expr
'[' formlist ']' EQ_ASSIGN expr
expr RIGHT_ASSIGN '[' formlist ']'
where `formlist` has the syntax of the formals list for a function
definition. This would have the following semantics:
{
*tmp* <- expr
# For arguments with no "default" expression,
argname1 <- *...
2023 Mar 11
3
Multiple Assignment built into the R Interpreter?
...(including the corner cases, some of which you have
> > already mentioned). I'm not sure I'm up to the task.
> >
>
> If I were doing it, here's what I'd propose:
>
> '[' formlist ']' LEFT_ASSIGN expr
> '[' formlist ']' EQ_ASSIGN expr
> expr RIGHT_ASSIGN '[' formlist ']'
>
> where `formlist` has the syntax of the formals list for a function
> definition. This would have the following semantics:
>
> {
> *tmp* <- expr
>
> # For arguments with no "default&...
2018 Aug 16
0
Problem with parseData
...3, 14)"
> [6] "parseData = c(0, 3, 7, 7, 5, 7, 12, 0, 0, 14, 0)"
> [7] "parseData = c(\"expr\", \"SYMBOL\", \"expr\", \"LEFT_ASSIGN\",
> \"NUM_CONST\", \"expr\", \"SYMBOL\", \"expr\", \"EQ_ASSIGN\",
> \"NUM_CONST\", \"expr\")"
> [8] "parseData = c(FALSE, TRUE, FALSE, TRUE, TRUE, FALSE, TRUE, FALSE,
> TRUE, TRUE, FALSE)"
> [9] "parseData = c(\"y <- 5\", \"y\", \"y\", \"<-\", \"5\"...
2019 Jul 05
0
parse() drops parse data when encountering `` (bug?)
...> line1 col1 line2 col2 id parent token terminal text
#> 8 1 1 1 7 8 0 equal_assign FALSE
#> 1 1 1 1 3 1 3 SYMBOL TRUE foo
#> 3 1 1 1 3 3 8 expr FALSE
#> 2 1 5 1 5 2 8 EQ_ASSIGN TRUE =
#> 4 1 7 1 7 4 5 NUM_CONST TRUE 1
#> 5 1 7 1 7 5 8 expr FALSE
#> 6 1 9 1 9 6 0 '{' TRUE {
sessionInfo()
#> R version 3.6.0 (2019-04-26)
#> Platform: x86_64-pc-linux...
2023 Mar 11
1
Multiple Assignment built into the R Interpreter?
...s, some of which you have
> > already mentioned). I'm not sure I'm up to the task.
> >
>
> If I were doing it, here's what I'd propose:
>
> ? ?'[' formlist ']' LEFT_ASSIGN expr
> ? ?'[' formlist ']' EQ_ASSIGN expr
> ? ?expr RIGHT_ASSIGN? '[' formlist ']'
>
> where `formlist` has the syntax of the formals list for a function
> definition.? This would have the following semantics:
>
> ? ? {
> ? ? ? *tmp* <- expr
>
> ? ? ? # For a...
2023 Mar 11
2
Multiple Assignment built into the R Interpreter?
...t; > already mentioned). I'm not sure I'm up to the task.
> > >
> >
> > If I were doing it, here's what I'd propose:
> >
> > '[' formlist ']' LEFT_ASSIGN expr
> > '[' formlist ']' EQ_ASSIGN expr
> > expr RIGHT_ASSIGN '[' formlist ']'
> >
> > where `formlist` has the syntax of the formals list for a function
> > definition. This would have the following semantics:
> >
> > {
> > *tmp* <- e...
2023 Mar 11
1
Multiple Assignment built into the R Interpreter?
On Sat, 11 Mar 2023 11:11:06 -0500
Duncan Murdoch <murdoch.duncan at gmail.com> wrote:
> That's clear, but your proposal violates a very basic property of the
> language, i.e. that all statements are expressions and have a value.
How about reframing this feature request from multiple assignment
(which does go contrary to "everything has only one value, even if it's
2023 Mar 12
2
Multiple Assignment built into the R Interpreter?
...). I'm not sure I'm up to the task.
> > > >
> > >
> > > If I were doing it, here's what I'd propose:
> > >
> > > '[' formlist ']' LEFT_ASSIGN expr
> > > '[' formlist ']' EQ_ASSIGN expr
> > > expr RIGHT_ASSIGN '[' formlist ']'
> > >
> > > where `formlist` has the syntax of the formals list for a function
> > > definition. This would have the following semantics:
> > >
> > > {
>...
2023 Mar 11
1
Multiple Assignment built into the R Interpreter?
...f which you have
> > > already mentioned). I'm not sure I'm up to the task.
> > >
> >
> > If I were doing it, here's what I'd propose:
> >
> > '[' formlist ']' LEFT_ASSIGN expr
> > '[' formlist ']' EQ_ASSIGN expr
> > expr RIGHT_ASSIGN '[' formlist ']'
> >
> > where `formlist` has the syntax of the formals list for a function
> > definition. This would have the following semantics:
> >
> > {
> > *tmp* <- expr
> >
> >...
2023 Mar 12
1
Multiple Assignment built into the R Interpreter?
...> >? ? ? >
> > >
> > >? ? ?If I were doing it, here's what I'd propose:
> > >
> > >? ? ? ? ?'[' formlist ']' LEFT_ASSIGN expr
> > >? ? ? ? ?'[' formlist ']' EQ_ASSIGN expr
> > >? ? ? ? ?expr RIGHT_ASSIGN? '[' formlist ']'
> > >
> > >? ? ?where `formlist` has the syntax of the formals list for
> a function
> > >? ? ?definition.? This would have the following semanti...
2023 Mar 12
1
Multiple Assignment built into the R Interpreter?
...gt; > > >
> > > > If I were doing it, here's what I'd propose:
> > > >
> > > > '[' formlist ']' LEFT_ASSIGN expr
> > > > '[' formlist ']' EQ_ASSIGN expr
> > > > expr RIGHT_ASSIGN '[' formlist ']'
> > > >
> > > > where `formlist` has the syntax of the formals list for
> > a function
> > > > definition. This would h...
2023 Mar 13
1
Multiple Assignment built into the R Interpreter?
...t; >
> > > ???????? > >???? If I were doing it, here's what I'd propose:
> > > ???????? > >
> > > ???????? > >???????? '[' formlist ']' LEFT_ASSIGN expr
> > > ???????? > >???????? '[' formlist ']' EQ_ASSIGN expr
> > > ???????? > >???????? expr RIGHT_ASSIGN? '[' formlist ']'
> > > ???????? > >
> > > ???????? > >???? where `formlist` has the syntax of the formals
> > > list for
> > > ??????? a function
> > > ????????...
2023 Mar 13
1
Multiple Assignment built into the R Interpreter?
...>>> ???????? > >???? If I were doing it, here's what I'd propose:
>>>> ???????? > >
>>>> ???????? > >???????? '[' formlist ']' LEFT_ASSIGN expr
>>>> ???????? > >???????? '[' formlist ']' EQ_ASSIGN expr
>>>> ???????? > >???????? expr RIGHT_ASSIGN? '[' formlist ']'
>>>> ???????? > >
>>>> ???????? > >???? where `formlist` has the syntax of the formals
>>>> list for
>>>> ??????? a function
>>&...