Displaying 3 results from an estimated 3 matches for "l347".
Did you mean:
2347
2023 Apr 16
1
Unique ID for conditions to supress/rethrow selected conditions?
....
A "simple" solution could be to pre- or postfix each message text with an ID, for example this code here
else errorcall(call, _("non-numeric argument to function"));
# https://github.com/r-devel/r-svn/blob/49597237842697595755415cf9147da26c8d1088/src/main/complex.c#L347
would become
else errorcall(call, _("non-numeric argument to function [47]"));
or
else errorcall(call, _("[47] non-numeric argument to function"));
Now the ID could be extracted more easily (at least for base R condition messages)...
This would even be back-portabl...
2023 Apr 16
1
Unique ID for conditions to supress/rethrow selected conditions?
On Sun, 16 Apr 2023 at 12:58, nospam at altfeld-im.de <nospam at altfeld-im.de> wrote:
>
> 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
2019 Apr 04
2
single-threaded code-gen and how to make it support multi-thread
Thank you Johannes, I looked it up and it seems that we're creating one
LLVMContext per compilation "unit", not sure if that matters. i.e. there's
no single globally shared LLVMContext object.
Is LLVMContext *the* concurrency isolation (or unit) here?
On Wed, Apr 3, 2019 at 6:34 PM Doerfert, Johannes <jdoerfert at anl.gov> wrote:
> Do you use one llvm context or one