search for: errorcondit

...of work) to define a hierarchy of built-in conditions, and then use them consistently throughout base R. For example, > 1 + "a" Error in 1 + "a" : non-numeric argument to binary operator could be a "typeError". And catching this is already possible: > e <- errorCondition("non-numeric argument to binary operator", class="typeError") > tryCatch(stop(e), typeError=function(e) print("hello")) [1] "hello" -- I?aki ?car

I am the author of the *tryCatchLog* package and want to - suppress selected conditions (warnings and messages) - rethrow selected conditions (e.g a specific warning as a message or to "rename" the condition text). I could not find any reliable unique identifier for each possible condition - that (base) R throws - that 3rd-party packages can throw (out of scope here). Is there any

...tibility. * palette.colors() gains a name argument that defaults to FALSE controlling whether the vector of colours that is returned has names (where possible). PR#18529. * tools::xgettext() no longer extracts the (non-translatable) class names from warningCondition and errorCondition calls. * S3method(<gen>, <class>, <func>) in the NAMESPACE file now works (again) when <func> is visible from the namespace, e.g., imported, or in base. * getParseData(f) now also works for a function defined in the first of several <pkg>...

...tibility. * palette.colors() gains a name argument that defaults to FALSE controlling whether the vector of colours that is returned has names (where possible). PR#18529. * tools::xgettext() no longer extracts the (non-translatable) class names from warningCondition and errorCondition calls. * S3method(<gen>, <class>, <func>) in the NAMESPACE file now works (again) when <func> is visible from the namespace, e.g., imported, or in base. * getParseData(f) now also works for a function defined in the first of several <pkg>...

...support_old_tars whose default is controlled by environment variable R_SUPPORT_OLD_TARS. (It looks like NetBSD and OpenBSD have 'older' tar commands for this purpose.) * The new function asplit() allow splitting an array or matrix by its margins. * New functions errorCondition() and warningCondition() provide a convenient way to create structured error and warning objects. .Deprecated() now signals a warning of class "deprecatedWarning", and .Defunct() now signals an error of class "defunctError". * Many 'package not fou...

...support_old_tars whose default is controlled by environment variable R_SUPPORT_OLD_TARS. (It looks like NetBSD and OpenBSD have 'older' tar commands for this purpose.) * The new function asplit() allow splitting an array or matrix by its margins. * New functions errorCondition() and warningCondition() provide a convenient way to create structured error and warning objects. .Deprecated() now signals a warning of class "deprecatedWarning", and .Defunct() now signals an error of class "defunctError". * Many 'package not fou...

...support_old_tars whose default is controlled by environment variable R_SUPPORT_OLD_TARS. (It looks like NetBSD and OpenBSD have 'older' tar commands for this purpose.) * The new function asplit() allow splitting an array or matrix by its margins. * New functions errorCondition() and warningCondition() provide a convenient way to create structured error and warning objects. .Deprecated() now signals a warning of class "deprecatedWarning", and .Defunct() now signals an error of class "defunctError". * Many 'package not fou...