File: javaImport.Rd

package info (click to toggle)
rjava 1.0-11-2
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 3,184 kB
  • sloc: java: 13,223; ansic: 5,479; sh: 3,776; xml: 325; makefile: 250; perl: 33
file content (56 lines) | stat: -rw-r--r-- 1,257 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
\name{javaImport}
\alias{javaImport}
\title{
Attach mechanism for java packages
}
\description{
The \code{javaImport} function creates an item on R's
search that maps names to class names references found in 
one or several "imported" java packages.
}
\usage{
javaImport(packages = "java.lang")
}
\arguments{
  \item{packages}{character vector containing java package paths}
}
\value{
An external pointer to a java specific \code{UserDefinedDatabase} object
}
\references{
	\emph{User-Defined Tables in the R Search Path}. Duncan Temple Lang. December 4, 2001
	\url{https://www.omegahat.net/RObjectTables/}
}
\author{
Romain Francois <francoisromain@free.fr>
}
\note{
Currently the list of objects in the imported package is populated
as new objects are found, \emph{not} at creation time.
}
\section{Warning}{
This feature is experimental. Use with caution, and don't forget to
detach.
}
\seealso{
\code{\link{attach}}
}
\examples{
\dontrun{
	attach( javaImport( "java.util" ), pos = 2 , name = "java:java.util" )
	
	# now we can just do something like this 
	v <- new( Vector )
	v$add( "foobar" )
	ls( pos = 2 )
	
	# or this
	m <- new( HashMap )
	m$put( "foo", "bar" )
	ls( pos = 2 )
	
	# or even this :
	Collections$EMPTY_MAP
}
}
\keyword{ programming }