similar to: RE: [R] debugging non-visible functions

On Wed, 13 Oct 2004, Duncan Temple Lang wrote: > Prof Brian Ripley wrote: > > On Wed, 13 Oct 2004, Liaw, Andy wrote: > > > > > > > On a slightly different topic: In R-2.0.0, packages with NAMESPACE no > > > longer need to use the package= argument in .C/.Fortran. Does that mean if > > > I remove those arguments, I should put R version >=

[I'm diverting this to R-devel, as I believe my questions are more appropriate for that.] > From: Prof Brian Ripley [snip] > Luke Tierney recommends removing the NAMESPACE file during > development of > a package if you need frequent access to debug/change its functions. But isn't that a bit troublesome if there is a shared object to be loaded in the NAMESPACE file? If I

--d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Prof Brian Ripley wrote: > nor in any sensible way we could document. >=20 > In R 2.0.0 (and current R-patched and R-devel): >=20 > > X11() > > library.dynam() > Filename Dynamic.Lookup >

Hi: I'm using RSPerl_0.6-3 calling R from Perl under UNIX system. My perl programs with the RSPerl work well in my computer. If submitting these programs to a UNIX system by 'ssh' or to GNQS system by 'qsub', these programs do not work even though both systems can run R. Details are following. Any suggestion will be highly appreciated. Xiao My perl program 'tt.pl'

> From: Philippe Grosjean > > Duncan, > > I agree totally with you on all points, now that we clarified our > respective ideas. I am afraid I probably agree also with your last > point, from a theoretical point-of-view ("I still think we need more > glue and am working on that while we continue to experiment with the > design of GUIs for the next 5 years

Duncan, you are a king! Thanks a lot for this cookie. It really helped me. Thanks for the code as well as detailed explanation at the end. >Hi Gregor. > >Here is a function that will collect all of the nodes in the >XML document whose names are in the vector elementNames > >getElements = >function(elementNames) >{ > els = list() > > startElement = function(node,

Hi, Prof Duncan I am sorry to report to a wrong place. But I am lucky to meet you by chance, right? Thanks first ^^ 1. The variable y1 is an array get from Perl, each element is from a database (the type should be numeric). Here is the code for that. $query = qq{ select exonCount, count(hsEnsGene) as geneCount from countTop1000ks group by exonCount order by exonCount;

Hi, Prof Duncan I am sorry to report to a wrong place. But I am lucky to meet you by chance, right? Thanks first ^^ 1. The variable y1 is an array get from Perl, each element is from a database (the type should be numeric). Here is the code for that. $query = qq{ select exonCount, count(hsEnsGene) as geneCount from countTop1000ks group by exonCount order by exonCount;

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I happened to be looking at that myself yesterday. It is relatively easy to get the package name from the DESCRIPTION file and not the directory name. But there are other issues. I'll look into this further in a week or two. D. ahenningsen at agric-econ.uni-kiel.de wrote: > Full_Name: Arne Henningsen > Version: >= 2.3.0 > OS: Linux

Filing on R-bugs (DTL's reply started a new PR). -- Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595 ---------- Forwarded message

Duncan, I don't know what we want, but it is not a simple matter of documenting what .dynLibs currently does. What I see as bugs are 1) the inconsistent names and types of the components returned by .dynLibs(). 2) the inconsistent inclusion or not of R_X11 in the list returned by .dynLibs(). 3) the inclusion of static info (base) by library.dynam(). 4) including loadable modules

On Wed, 20 Dec 2000 joehl@web.de wrote: > I expected close() to be the opposite of open(), but Why? It is not documented to be so, as far as I know. > > # create a connection > > con <- file("ex.data") > > # open it > > open(con, "w") > > # close it > > close(con) > > # re-open it > > open(con, "w") > Error

Mac OS 10.3.5, R 2.0.0 latest version of geoR I have an incomplete 5 x 20 spatial array of samples (60 out of 100 possible locations) for which I would like to calculate directional variograms using variog4(). Unfortunately, I can't get it to return all 4 directions. It returns variograms for 45, 90, and 135 degrees, omitting 0 degrees (pi/4, pi/2, 3pi/4, omitting 0). If I specify 0

Hi, I am running a correlation analysis on a temporal dataset. I was wondering if you would receive the same tau and p values running the function: MannKendall(x), where x is the dependant variable that changes with time as you would running: Kendall(d,x), where x is the exact same dataset as the x entered into MannKendall and d is the date on which the observation was made (assuming that

I've added to R-devel the ability to use download.file() and url() to https: URLs, *only* if --internet2 is used on Windows. This uses the Internet Explorer internals, and only works if the certificate is accepted (so e.g. does not work for https://svn.r-project.org). Now I use IE (and Windows for that matter) only when really necessary, and Firefox has simple ways to permanently accept

I and my students have been having an odd problem with this release, which is that packages are disappearing. After installation the package is found with the library command, but later in the same session or in a later session, the library command returns a not found error. Then later it is back. Happening on both Windows and OS X, mostly but not entirely with Bioconductor packages. David

The R_registerRoutines C function allows the number of parameters to a .Call function to be registered. For example, the tools package function md5sum() calls "Rmd5", which has been registered to require just one parameter. But if it is called with the wrong number of parameters, only the first error gets caught: > library(tools) >

> From: Duncan Murdoch [snip] > For 2.1.0, would it be reasonable to extend debug() the way ? was > extended? E.g. allow > > debug(plot(x)) > > and have the debugging flag be set on the appropriate function, > whatever and wherever it happens to be? There's some ambiguity with > S3 methods (did you want to debug the generic or the method?), but I > think

On Fri, 29 Jun 2007, John Criswell wrote: > Chris Lattner wrote: >> On Fri, 29 Jun 2007, John Criswell wrote: >>> The LLVM web server is up and running, but we're still working on some >>> subversion configuration issues. The server may go up and down >>> intermittently as we try configuration changes over the next half hour. >>> >> >>

Hi, I would like to step-through a non-visible function. but apparently I don't know enough about namespaces to get that to work: > methods(predict) ... deleted lines ... [27] predict.rpart* predict.smooth.spline* [31] predict.survreg.penal* Non-visible functions are asterisked > debug(predict.rpart) Error: Object "predict.rpart" not found >