search for: vankerschav

Displaying 3 results from an estimated 3 matches for "vankerschav".

2023 Mar 15
0
R 4.2.3 is released
...eport (including patch) in PR#18448. * solve.default(a, b) works around issues with some versions of LAPACK when a contains NA or NaN values. * When UseMethod() cannot dispatch, it no longer segfaults producing the error message in case of a long class(), thanks to Joris Vankerschaver's report (including patch) in PR#18447. * When example(foo, ..) produces graphics on an interactive device it needs to open itself, it now leaves devAskNewPage() unchanged even when it was FALSE, thus fixing a 14 years old '<FIXME>'. * packageDescription()...
2023 Mar 15
0
R 4.2.3 is released
...eport (including patch) in PR#18448. * solve.default(a, b) works around issues with some versions of LAPACK when a contains NA or NaN values. * When UseMethod() cannot dispatch, it no longer segfaults producing the error message in case of a long class(), thanks to Joris Vankerschaver's report (including patch) in PR#18447. * When example(foo, ..) produces graphics on an interactive device it needs to open itself, it now leaves devAskNewPage() unchanged even when it was FALSE, thus fixing a 14 years old '<FIXME>'. * packageDescription()...
2023 Mar 15
0
R 4.2.3 is released
...eport (including patch) in PR#18448. * solve.default(a, b) works around issues with some versions of LAPACK when a contains NA or NaN values. * When UseMethod() cannot dispatch, it no longer segfaults producing the error message in case of a long class(), thanks to Joris Vankerschaver's report (including patch) in PR#18447. * When example(foo, ..) produces graphics on an interactive device it needs to open itself, it now leaves devAskNewPage() unchanged even when it was FALSE, thus fixing a 14 years old '<FIXME>'. * packageDescription()...