search for: incomplete_str

...en it is a part of literal string. For example if i copy the following to the clipboard confuse.tidy <-    function() {   txt <- 'abra # cadabra' } and run with default arguments >tidy.source() I am getting Error in base::parse(text = text, srcfile = NULL) :    4:46: unexpected INCOMPLETE_STRING 4: txt <- 'abra  %InLiNe_IdEnTiFiEr% "# cadabra'" 5: } However, good news, as i realized after a bit of struggle, is that i could do  >tidy.source(keep.comment=F) which produces desired  confuse.tidy <- function() {     txt <- "abra # cadabra" } Unfo...

...re sourcing fine when they are encoded in the systems CP1251 encoding). Let's consider the following script that prints random russian words: > > > *print("?????")print("????")print("???????")print("????")* When this script is sourced we get INCOMPLETE_STRING error: > > > > > *source('D:/R code/test_cyr_letter.R', encoding = 'UTF-8', echo=TRUE)Error > in source("D:/R code/test_cyr_letter.R", encoding = "UTF-8", echo = TRUE) > : D:/R code/test_cyr_letter.R:3:7: unexpected INCOMPLETE_STRING2:...

...cing fine when they are encoded in the systems CP1251 encoding). Let's consider the following script that prints random russian words: >/ />/ />/ *print("?????")print("????")print("???????")print("????")* / When this script is sourced we get INCOMPLETE_STRING error: >/ />/ />/ />/ />/ *source('D:/R code/test_cyr_letter.R', encoding = 'UTF-8', echo=TRUE)Error />/ in source("D:/R code/test_cyr_letter.R", encoding = "UTF-8", echo = TRUE) />/ : D:/R code/test_cyr_letter.R:3:7: unexpected INC...

...parsing is shown below: o The new parser fixes bugs arising from the old parser's kludge to handle semicolons, illustrated by the incorrect output seen below: > p<-parse() ?"abc;xyz" Error in parse() : <stdin>:1:1: unexpected INCOMPLETE_STRING 1: "abc; ^ > p<-parse() ?8 #abc;xyz Error in parse() : <stdin>:1:7: unexpected end of input 1: 8 #abc; ^ o Fixed deparsing of complex numbers, which were always deparsed as the sum of a real and an im...