On 05/05/2017 2:09 PM, Mark wrote:
Hi Uwe,
Thank you, I have a series of cc files that use similar function names, so to
avoid overriding functions, I thought to compile and load each of the cc files
separately. In more detail, I have a series of models for the use in deSolve,
they all have t
Hi Uwe,
Thank you, I have a series of cc files that use similar function names, so to
avoid overriding functions, I thought to compile and load each of the cc files
separately. In more detail, I have a series of models for the use in deSolve,
they all have the same initmod and derivs internal
Thanks Duncan. Your suggestion gave me an error message that I could
understand and fix it. It was a "Runaway argument" in the first line.
As I often say, a day without learning something is a day wasted.
Jim
On Fri, May 5, 2017 at 8:00 PM, Duncan Murdoch wrote:
> On 05/05/2017 5:47 AM, Jim Lem
On 05/05/2017 5:47 AM, Jim Lemon wrote:
Hi,
In adding a contributed function to the plotrix package, I keep
getting a latex error:
* checking PDF version of manual ... WARNING
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
LaTeX errors found:
! File ended while sca
Hi,
In adding a contributed function to the plotrix package, I keep
getting a latex error:
* checking PDF version of manual ... WARNING
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
LaTeX errors found:
! File ended while scanning use of \HeaderA.
\pa
Why do you want to build separate dll files if you want to load all of
them anyway? That way you add some overhead, at least.
From Writing R Extensions:
"A few packages use the src directory for purposes other than making a
shared object (e.g. to create executables). Such packages should have