Re: [R-pkg-devel] truncating strings on purpose

2024-12-11 Thread Iris Simmons
You could use memcpy instead. That gets rids of the type checking though. You could also define something like char * my_strncpy ( char * destination, const char * source, size_t num ) { return (char *) memcpy(destination, source, num) } to keep the type checking. On Wed, Dec 11, 2024, 07:12 Brad

Re: [R-pkg-devel] truncating strings on purpose

2024-12-11 Thread Ivan Krylov via R-package-devel
В Wed, 11 Dec 2024 12:12:11 + Brad Eck пишет: > Found the following significant warnings: > input2.c:863:5: warning: ‘__builtin_strncpy’ output may be > truncated copying 225 bytes from a string of length 255 > [-Wstringop-truncation] > Where the truncation warnings appear, I am truncati

[R-pkg-devel] truncating strings on purpose

2024-12-11 Thread Brad Eck
Dear List The latest update to my epanet2toolkit package bounced from CRAN due to some warnings about string truncation in C code from gcc. Found the following significant warnings: input2.c:863:5: warning: ‘__builtin_strncpy’ output may be truncated copying 225 bytes from a string of length

Re: [R-pkg-devel] Creating and hosting static libraries for package installation on Windows

2024-12-11 Thread Uwe Ligges
We really want to get rid of having compiled code imported during the installation process. Ideally talk to Tomas Kalibera to get the libraries you need included in to the next Rtools update. Best, Uwe Ligges On 11.12.2024 05:23, Satyaprakash Nayak wrote: Hi r-package-devel I am working on