search for: getpackagenam

...;) >unloadNamespace('data.table') It produces some warnings Warning in FUN(X[[1L]], ...) : Created a package name, ‘2013-10-29 17:05:51’, when none found Warning in FUN(X[[1L]], ...) : Created a package name, ‘2013-10-29 17:05:51’, when none found ... The warning is produced by the getPackageName() function. e.g. getPackageName(parent.env(getNamespace('data.table'))) I was wondering what could be done to get rid of these warnings, which I believe in the case "unloadNamespace" case are irrelevant. The stack of calls is: # where 3: sapply(where, getPackageName) # where 4:...

The function getAllMethods in the methods package uses the non-existent function packageName where I believe the function getPackageName was intended. For example: > getAllMethods("formula") Error in sprintf(gettext(fmt, domain = domain), ...) : could not find function "packageName" The patch to RMethodUtils.R is here: 238c238 < warning(gettextf("'%s' from '%s' is a...

...i Harris Bakiras, Thanks for reply. It working now. Actually I wanted to try vmkit VM to run jruby codes. vmkit is able to run Java program, but when I try to run JRuby code then I get following error - root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb > > Platform.java:39:in `getPackageName': java.lang.NullPointerException > > from ConstantSet.java:84:in `getEnumClass' > > from ConstantSet.java:60:in `getConstantSet' > > from ConstantResolver.java:181:in `getConstants' > > from ConstantResolver.java:102:in `getConstant' > > from Const...

...(revision 41719) +++ RMethodUtils.R (working copy) @@ -621,7 +621,7 @@ getMethodsMetaData <- ## get the methods meta-data for function f on database where function(f, where = topenv(parent.frame())) { - mname <- mlistMetaName(f, where) + mname <- mlistMetaName(f, getPackageName(where)) if(exists(mname, where = where, inherits = missing(where))) get(mname, where) else Seth Falcon <sfalcon at fhcrc.org> writes: > cstrato <cstrato at aon.at> writes: > >> Dear all, >> >> What is the best way to write the do...

...working now. > Actually I wanted to try vmkit VM to run jruby codes. > > vmkit is able to run Java program, but when I try to run JRuby code then > I get following error - > > root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb >> >> Platform.java:39:in `getPackageName': java.lang.NullPointerException >> >> from ConstantSet.java:84:in `getEnumClass' >> >> from ConstantSet.java:60:in `getConstantSet' >> >> from ConstantResolver.java:181:in `getConstants' >> >> from ConstantResolver.java:102:in `g...

...now. > Actually I wanted to try vmkit VM to run jruby codes. > > vmkit is able to run Java program, but when I try to run JRuby code > then I get following error - > > root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb > > Platform.java:39:in `getPackageName': > java.lang.NullPointerException > > from ConstantSet.java:84:in `getEnumClass' > > from ConstantSet.java:60:in `getConstantSet' > > from ConstantResolver.java:181:in `getConstants' > > from ConstantResolver.java:...

...I wanted to try vmkit VM to run jruby codes. >> >> vmkit is able to run Java program, but when I try to run JRuby code >> then I get following error - >> >> root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb >>> >>> Platform.java:39:in `getPackageName': java.lang.NullPointerException >>> >>> from ConstantSet.java:84:in `getEnumClass' >>> >>> from ConstantSet.java:60:in `getConstantSet' >>> >>> from ConstantResolver.java:181:in `getConstants' >>> >>> from...

...rs <- character() + generics <- character() + packages <- character() allFuns <- methods:::.getGenerics(ns) # all the methods tables in ns - packages <- attr(allFuns, "package") + allPackages <- attr(allFuns, "package") pkg <- methods:::getPackageName(ns) if(!all(vars %in% allFuns)) { message(gettextf("No methods found in \"%s\" for requests: %s", @@ -950,16 +952,23 @@ ## import methods tables if asked for ## or if the corresponding generic was imported g <- allFuns[[i]] + p...

...M to run jruby codes. >> >> vmkit is able to run Java program, but when I try to run JRuby >> code then I get following error - >> >> root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb >> >> Platform.java:39:in `getPackageName': >> java.lang.NullPointerException >> >> from ConstantSet.java:84:in `getEnumClass' >> >> from ConstantSet.java:60:in `getConstantSet' >> >> from ConstantResolver.java:181:in `getConstants' &...

...run jruby codes. >>> >>> vmkit is able to run Java program, but when I try to run JRuby code >>> then I get following error - >>> >>> root at komal:/home/komal/Desktop/GSOC/programs# jruby hello.rb >>>> >>>> Platform.java:39:in `getPackageName': java.lang.NullPointerException >>>> >>>> from ConstantSet.java:84:in `getEnumClass' >>>> >>>> from ConstantSet.java:60:in `getConstantSet' >>>> >>>> from ConstantResolver.java:181:in `getConstants' >&gt...

Hi Kumar, There is an error on your configuration line, you should provide the path to llvm-config binary instead of configure file. Assuming that you compiled llvm in release mode, the llvm-config binary is located in : YOUR_PATH_TO_LLVM/Release+Asserts/bin/llvm-config Try to change the -with-llvm-config-path option and it will compile. Harris Bakiras On 07/19/2013 02:36 PM, Kumar

How do you debug methods of a reference class? I've been using mtrace, which is excellent, but i cannot figure out how to mtrace a reference class method. Maybe there is some other way to debug these, for example with ordinary trace? for now i am only able to use options(error=recover), which is not giving me idea where exactly in the code i am once i am stopped on an error. -- View this

To compile vmkit on Ubuntu 12.04 64-bit machine, I followed the steps giving here <http://vmkit.llvm.org/get_started.html>[1]. but when I run ./configure I am getting following error- root at komal:/home/komal/Desktop/GSOC/vmkit/vmkit# ./configure >> -with-llvm-config-path=../llvm-3.3.src/configure >> --with-gnu-classpath-glibj=/usr/local/classpath/share/classpath/glibj.zip

I've run into a problem that I hope has an obvious solution. The sp package uses S4 classes and has a NAMESPACE, and when installed without package versions, runs OK, passes R CMD check, and so on. A user reported that he installed it --with-package-versions, and that from then on it would fail at first use of a class defined in the package. I've reconstructed the problem in a

...###### Related code from "methods" package: cacheMetaData <- function(where, attach = TRUE, searchWhere = as.environment(where), doCheck = TRUE) { ## a collection of actions performed on attach or detach ## to update class and method information. pkg <- getPackageName(where) classes <- getClasses(where) for(cl in classes) { cldef <- (if(attach) get(classMetaName(cl), where) # NOT getClassDef, it will use cache else getClassDef(cl, searchWhere)) if(is(cldef, "classRepresentation")) { if(attac...

..."3.6.2" > stopifnot(require("myTst",lib = "myLib")) Loading required package: myTst > sm <- findMethods(show, where= as.environment("package:myTst")) > stopifnot(names(sm at names) == "foo") > unlink("myTst_*") > > ## getPackageName() for "package:foo": > require('methods') > library(tools) > oo <- options(warn=2) > detach("package:tools", unload=TRUE) > options(oo) > ## gave warning (-> Error) about creating package name > > > ## More building & installing p...

...ting new S4 class and method definitions in an environment that could not be identified (as package, namespace or global) previously generated an error. It now results in creating and using an artificial package name from the current date/time, with a warning. See ?getPackageName. o Unix-alikes now give a warning on startup if locale settings fail. (The Windows port has long done so.) o Parsing and scanning of numerical constants is now done by R's own C code. This ensures cross-platform consistency, and mitigates the effects of...

...ting new S4 class and method definitions in an environment that could not be identified (as package, namespace or global) previously generated an error. It now results in creating and using an artificial package name from the current date/time, with a warning. See ?getPackageName. o Unix-alikes now give a warning on startup if locale settings fail. (The Windows port has long done so.) o Parsing and scanning of numerical constants is now done by R's own C code. This ensures cross-platform consistency, and mitigates the effects of...

...lt; table of extent 0 x 1 x 2 >. (Wish of PR#15198.) o Deparsing involving calls to anonymous functions and has been made closer to reversible by the addition of extra parentheses. o The function utils::packageName() has been added as a lightweight version of methods::getPackageName(). o find.package(lib.loc = NULL) now treats loaded namespaces preferentially in the same way as attached packages have been for a long time. o In Windows, the Change Directory dialog now defaults to the current working directory, rather than to the last directory...

...lt; table of extent 0 x 1 x 2 >. (Wish of PR#15198.) o Deparsing involving calls to anonymous functions and has been made closer to reversible by the addition of extra parentheses. o The function utils::packageName() has been added as a lightweight version of methods::getPackageName(). o find.package(lib.loc = NULL) now treats loaded namespaces preferentially in the same way as attached packages have been for a long time. o In Windows, the Change Directory dialog now defaults to the current working directory, rather than to the last directory...