[R] How to *completely* stop a script after stop()?
wdunlap at tibco.com
Fri Apr 8 18:40:02 CEST 2011
Put an open brace in the first line of your file
and a close brace in the last line.
I encourage people with scripts long enough that this
is a problem to divide up their work into functions
that a shorter script calls. (This is akin to UCSD
Pascal on the Osbourne II that refused to deal with
a function that could not fit onto the tiny screen
-- it forced you do divide things up into small
understandable chunks of work.)
Spotfire, TIBCO Software
> -----Original Message-----
> From: r-help-bounces at r-project.org
> [mailto:r-help-bounces at r-project.org] On Behalf Of algorimancer
> Sent: Friday, April 08, 2011 8:47 AM
> To: r-help at r-project.org
> Subject: Re: [R] How to *completely* stop a script after stop()?
> I too am encountering this problem. When I have a large
> script, if I select
> all in the editor and then ctrl-r to run, if it encounters a
> stop() function
> it simply prints an error message and continues to execute
> the remainder of
> the script, as opposed to terminating execution at that line.
> The quit()
> function exits R altogether, which I don't want. Yes, I
> could manually
> select only the portion of script which I want to run, but for lengthy
> scripts which I run repeatedly (generally changing only the
> name of the file
> I want analyzed), this can be quite tedious. It appears that the only
> solution is to put most of the code in a separate file and
> call it using
> source(); this has the downside of reducing the clarity of
> the code -- it's
> a sort-of structural spaghetti code approach.
> View this message in context:
> Sent from the R help mailing list archive at Nabble.com.
> R-help at r-project.org mailing list
> PLEASE do read the posting guide
> and provide commented, minimal, self-contained, reproducible code.
More information about the R-help