[R] Inspecting C code in an R package
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 package. Does someone know, where the corresponding C-Code ist stored, so I could inspect it and comprehend what is happening? Thank you very much in advance! Regards Roman -- View this message in context: http://r.789695.n4.nabble.com/Inspecting-C-code-in-an-R-package-tp3590596p3590596.html Sent from the R help mailing list archive at Nabble.com. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Inspecting C code in an R package
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 romanhorn...@web.de wrote: 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 package. Does someone know, where the corresponding C-Code ist stored, so I could inspect it and comprehend what is happening? Thank you very much in advance! Regards Roman -- Sarah Goslee http://www.functionaldiversity.org __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Inspecting C code in an R package
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.nabble.com/Inspecting-C-code-in-an-R-package-tp3590596p3590641.html Sent from the R help mailing list archive at Nabble.com. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Inspecting C code in an R package
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:jdnew...@dcn.davis.ca.us Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/Batteries O.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...1k --- Sent from my phone. Please excuse my brevity. Layman123 romanhorn...@web.de wrote: 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 package. Does someone know, where the corresponding C-Code ist stored, so I could inspect it and comprehend what is happening? Thank you very much in advance! Regards Roman -- View this message in context: http://r.789695.n4.nabble.com/Inspecting-C-code-in-an-R-package-tp3590596p3590596.html Sent from the R help mailing list archive at Nabble.com. _ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. [[alternative HTML version deleted]] __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Inspecting C code in an R package
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-an-R-package-tp3590596p3590744.html Sent from the R help mailing list archive at Nabble.com. __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
Re: [R] Inspecting C code in an R package
On Sat, Jun 11, 2011 at 5:31 PM, Layman123 romanhorn...@web.de 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 this will also find every time that function is called in the C files. And also anytime something called somename2 is mentioned. Most decent programmers editors will parse code files and construct a little database of where all your functions are defined so you can quickly jump to the definition of a function. In emacs this is done with a thing called 'etags'. But this is now beyond the scope of R-help... Barry __ R-help@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
