Displaying 3 results from an estimated 3 matches for "suppresswarnigns".
2017 Dec 15
1
cannot destroy connection (?) created by readLines in a tryCatch
...ing_ handler for warnings is usually not what you
> want. If you are trying to suppress warnings you need to use a
> calling handler, e.g. via suppressWarnings. If you want to do
> something more sophisticated that does not terminate the
> computation on a warniing you can build on what suppressWarnigns
> does.
>
> Best,
>
> luke
>
>
> On Thu, 14 Dec 2017, G?bor Cs?rdi wrote:
>
>> On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu>
>> wrote:
>>>
>>> Gabor,
>>>
>>> You can grab the connection and...
2017 Dec 14
0
cannot destroy connection (?) created by readLines in a tryCatch
...stablishing
an _exiting_ handler for warnings is usually not what you
want. If you are trying to suppress warnings you need to use a
calling handler, e.g. via suppressWarnings. If you want to do
something more sophisticated that does not terminate the
computation on a warniing you can build on what suppressWarnigns
does.
Best,
luke
On Thu, 14 Dec 2017, G?bor Cs?rdi wrote:
> On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote:
>> Gabor,
>>
>> You can grab the connection and destroy it via getConnection and then a
>> standard close call.
>
>...
2017 Dec 14
4
cannot destroy connection (?) created by readLines in a tryCatch
On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote:
> Gabor,
>
> You can grab the connection and destroy it via getConnection and then a
> standard close call.
Yeah, that's often a possible workaround, but since this connection
was opened by
readLines() internally, I don't necessarily know which one it is. E.g.
I might open multiple