> Apparently this works:
> getNativeSymbolInfo("dotTcl",PACKAGE=getLoadedDLLs()$tcltk)
Thank you Peter! This solved the problem.
> and the tcltk behavior was changed by
> r84265 | hornik | 2023-04-15 08:44:36 +0200 (Sat, 15 Apr 2023) | 1 line
> Try forcing symbols in ff calls.
> I don't know wha
I have a use case with tcltk-package where I need to repeatedly call Tcl/Tk
functions
very quickly. For such purpose, the standard R-interface turned out to be too
slow, and
better option has been to call package's C-function dotTcl directly from my own
C-code.
Before R 4.4.0 it was possible to
st it gives a concrete example that hopefully stimulates discussion on
this topic..
Best wishes,
Reijo Sund
- - -
# Create environment for package's global variables
.muste <- new.env(hash=TRUE, parent=emptyenv())
muste <- function(config="")
{
# Package directory
> You only need ::: from outside the package.
In some cases I have had difficulties to evaluate non-exported/hidden R
functions from C code without ::: (inside the package). But that's a different
story and not any serious problem at all. Probably there is also some easy
workaround, but I haven
