We are hitting the MAX_ARGS ceiling in our R-C function calls in the
development of randomForestSRC. This limits to number of arguments to
65 using .Call(). Is there a work around for this dilemma? Thank
you.
Udaya B. Kogalur
u...@kogalur.com
Website: www.kogalur.com
On 20 February 2018 at 09:33, Udaya B. Kogalur wrote:
| We are hitting the MAX_ARGS ceiling in our R-C function calls in the
| development of randomForestSRC. This limits to number of arguments to
| 65 using .Call(). Is there a work around for this dilemma? Thank
| you.
The easiest is to avoid
Hi all,
I am using file-locking functions in C that can be found in the
in Unix
extern void flockfile (FILE *__stream) __THROW;
extern int ftrylockfile (FILE *__stream) __THROW __wur;
extern void funlockfile (FILE *__stream) __THROW;
When submitting to CRAN I have troubles with the win-builder