On 11/4/19 8:40 PM, Roy Mendelssohn - NOAA Federal via R-package-devel
wrote:
Hi All:
I am wondering if it is possible to find out when packages that use the netcdf
libraries are built on the CRAN machines (such as ncdf4) what versions of the
netcdf library are being used on at least Mac and W
I've just heard from another member of the client group and he cannot
reproduce the problem. I.e. he can install both the source package and
the binary that I sent out, without error.
So the problem seems to be in the system used by that first member of
the client group who contacted me.
I am developing a package ("ldEst" --- lethal dose estimation) for a
group of consulting clients. (The package may in the future be released
upon the unsuspecting public, but for the moment it has to stay
confidential, sad to say.)
The clients run Windoze (sad to say). In the past I have
Hi All:
I am wondering if it is possible to find out when packages that use the netcdf
libraries are built on the CRAN machines (such as ncdf4) what versions of the
netcdf library are being used on at least Mac and Windows?
If this is the wrong place to ask, please point me to where I should a
On 11/3/19 1:05 PM, Viktor Gal wrote:
ah yeah i forgot to mention. it’s the same, i.e. it’s not the byte code
compilation that causes this behaviour but the preparation for lazy loading.
R is not optimized for these cases (generated code, source file with
>100,000 lines of code), but R has bi
