CRAN Package Check Results for Package tomledit

Last updated on 2025-04-10 08:58:47 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	0.1.0	79.01	23.11	102.12	WARN
r-devel-linux-x86_64-debian-gcc	0.1.0	61.30	18.17	79.47	WARN
r-devel-linux-x86_64-fedora-clang	0.1.1			91.95	OK
r-devel-linux-x86_64-fedora-gcc	0.1.1			167.10	OK
r-devel-macos-arm64	0.1.1			47.00	OK
r-devel-macos-x86_64	0.1.1			122.00	OK
r-devel-windows-x86_64	0.1.0	79.00	56.00	135.00	NOTE
r-patched-linux-x86_64	0.1.0	79.04	22.36	101.40	WARN
r-release-linux-x86_64	0.1.0				OK
r-release-macos-arm64	0.1.1			55.00	OK
r-release-macos-x86_64	0.1.1			141.00	OK
r-release-windows-x86_64	0.1.0	85.00	51.00	136.00	OK
r-oldrel-macos-arm64	0.1.1			44.00	OK
r-oldrel-macos-x86_64	0.1.1			139.00	OK
r-oldrel-windows-x86_64	0.1.0	87.00	57.00	144.00	OK

Check Details

Version: 0.1.0
Check: compiled code
Result: WARN File ‘tomledit/libs/tomledit.so’: Found ‘abort’, possibly from ‘abort’ (C) Object: ‘rust/target/release/libtomledit.a’ File ‘tomledit/libs/tomledit.so’: Found non-API call to R: ‘DATAPTR’ Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-patched-linux-x86_64

Version: 0.1.0
Check: compiled code
Result: NOTE File 'tomledit/libs/x64/tomledit.dll': Found non-API call to R: 'DATAPTR' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64