On Sat, Jun 11, 2011 at 5:31 PM, Layman123 wrote:
> Thank you! Of course, I will read the posting guidelines. A subscriber helped
> me via e-mail telling me to use the grep-command, that is type in: grep
> "somename" *.c. For Windows users it's: findstr "somename" *.c.
The problem here is that t
Thank you! Of course, I will read the posting guidelines. A subscriber helped
me via e-mail telling me to use the grep-command, that is type in: grep
"somename" *.c. For Windows users it's: findstr "somename" *.c.
--
View this message in context:
http://r.789695.n4.nabble.com/Inspecting-C-code-in
Presumably in the source code of the package (something.tar.gz). Follow the
posting guidelines if you want further assistance.
---
Jeff Newmiller The . . Go Live...
DCN: Basics: ##.#. ##.#. Live Go...
Live: OO#.. Dead:
Thank you Sarah for your quick answer! I've just downloaded the source
package, but now I don't know in which file the C-Code is stored
".C("somename",)" is calling - there is no file with the name
"somename". How could one figure that out?
--
View this message in context:
http://r.789695.n4.
The easiest thing to do is download the source package from your local
CRAN mirror. That will contain all the R and other code.
Sarah
On Sat, Jun 11, 2011 at 10:50 AM, Layman123 wrote:
> Hello everyone,
>
> Trying to comprehend code of an R package, I encountered the problem that
> the interesti
Hello everyone,
Trying to comprehend code of an R package, I encountered the problem that
the interesting part of the
function I'm inspecting is written in C-Code and called by ".C("somename",
)". Now I can't inspect the C-Code the function is calling since I can't
find it in the folder of the
6 matches
Mail list logo
