Skip to content
Prev 256280 / 398506 Next

How to *completely* stop a script after stop()?

algorimancer 
Thank you all for the astoundingly quick responses.  I think that the
bounding open/closed braces approach sounds like the easiest solution for
the moment -- though I look forward to seeing this all automated in a future
version of R :)

Incidentally, I have indeed encapsulated much of the code as functions which
I call using source(); the problematic (lengthy) front-end is a decision
tree which tailors a specific analysis to designated files.  This mimics the
switch/case structure which I'm more familiar with in c/c++.  There's a
limit to how much can be neatly moved to a separate file.

Thank you again for your assistance.

--
View this message in context: http://r.789695.n4.nabble.com/How-to-completely-stop-a-script-after-stop-tp3218808p3437025.html
Sent from the R help mailing list archive at Nabble.com.

Thread (7 messages)

algorimancer How to *completely* stop a script after stop()? Apr 8 Duncan Murdoch How to *completely* stop a script after stop()? Apr 8 William Dunlap How to *completely* stop a script after stop()? Apr 8 Duncan Murdoch How to *completely* stop a script after stop()? Apr 8 Jonathan P Daily How to *completely* stop a script after stop()? Apr 8 Duncan Murdoch How to *completely* stop a script after stop()? Apr 8 algorimancer How to *completely* stop a script after stop()? Apr 8