R devel - Jun 2014 - Encourage exit with nonzero error status in ?last.dump

The following example in ?dump.frames

options(error = quote({dump.frames(to.file = TRUE); q()}))

is useful for teaching the user how to save a frame dump when R
encounters an error during non-interactive sessions. This command
however causes an additional change that on encountering an error R
exits with a 0 error status. Although it's just an example, it's an
important one as it's referenced in the 'Details' section of the
help
file. I think it would be better to encourage exiting with a nonzero
error status:

options(error = quote({dump.frames(to.file = TRUE); q(status = 1)}))

Scott


--
Scott Kostyshak
Economics PhD Candidate
Princeton University

>>>>> Scott Kostyshak <skostysh at princeton.edu>
>>>>>     on Fri, 13 Jun 2014 02:04:36 -0400 writes:
    > The following example in ?dump.frames options(error     >
quote({dump.frames(to.file = TRUE); q()}))

    > is useful for teaching the user how to save a frame dump
    > when R encounters an error during non-interactive
    > sessions. This command however causes an additional change
    > that on encountering an error R exits with a 0 error
    > status. Although it's just an example, it's an important
    > one as it's referenced in the 'Details' section of the
    > help file. I think it would be better to encourage exiting
    > with a nonzero error status:

    > options(error = quote({dump.frames(to.file = TRUE); q(status = 1)}))

You are right.  
Thank you for the suggestion: it will be in next
release.

Martin Maechler,
ETH Zurich