of course you never use it. it won't work. the point of the email is that writing an invalid statement should trigger only an error message. It should not trigger the segfault.
It looks like the segfault is specific to 3.0.1 since your and Marc both report that you don't see the segfault on 3.0.2 I will tell the student to upgrade to 3.0.2 immediately. On Thu, Oct 24, 2013 at 12:46 PM, Federico Calboli <f.calb...@imperial.ac.uk> wrote: > On 24 Oct 2013, at 17:37, Marc Schwartz <marc_schwa...@me.com> wrote: >> >> Rich, >> >> I get the same error message, but not the segfault, using 3.0.2 on >> Mavericks, using R.app: >> >> R version 3.0.2 (2013-09-25) -- "Frisbee Sailing" >> Copyright (C) 2013 The R Foundation for Statistical Computing >> Platform: x86_64-apple-darwin10.8.0 (64-bit) >> >> ... >> >> [R.app GUI 1.62 (6558) x86_64-apple-darwin10.8.0] >> >> which I otherwise never use. >> >>> >>> TRUE <- FALSE >> Error in TRUE <- FALSE : invalid (do_set) left-hand side to assignment >>> > > On Mountain Lion, R 3.0.2: > > TRUE = FALSE > Error in TRUE = FALSE : invalid (do_set) left-hand side to assignment > > in R.app, and in a terminal. I also get the same on a linux machine. > > I think that's a feature, not a bug. > > BW > > F _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
