[armedbear-cvs] r13657 - trunk/abcl/doc/manual
ehuelsmann at common-lisp.net
ehuelsmann at common-lisp.net
Fri Oct 21 21:07:31 UTC 2011
Author: ehuelsmann
Date: Fri Oct 21 14:07:31 2011
New Revision: 13657
Log:
Change date of transfer of maintainership.
Add description of more JAVA package primitives.
Modified:
trunk/abcl/doc/manual/abcl.tex
Modified: trunk/abcl/doc/manual/abcl.tex
==============================================================================
--- trunk/abcl/doc/manual/abcl.tex Fri Oct 21 13:59:01 2011 (r13656)
+++ trunk/abcl/doc/manual/abcl.tex Fri Oct 21 14:07:31 2011 (r13657)
@@ -297,6 +297,28 @@
The constructor can't be passed to \code{JAVA:JCALL}, but instead should
be passed as an argument to \code{JAVA:JNEW}.
+\subsubsection{Accessing Java object fields}
+
+Fields in Java objects can be accessed using the getter and setter functions
+\code{JAVA:GETFIELD} and \code{JAVA:PUTFIELD}. This applies to values stored in object
+instances. If you want to access static fields: see the next section.
+
+Like \code{JAVA:JCALL} and friends, values returned from these accessors carry
+an intended class around and values which can be converted to Lisp values will
+be converted.
+
+\subsubsection{Accessing Java static fields}
+
+Static fields in Java objects (class fields) can be accessed using the getter
+and setter functions \code{JAVA:GETSTATIC} and \code{JAVA:PUTSTATIC}. Values
+stored in object instance fields can be accessed as described in the previous
+section.
+
+Like \code{JAVA:JCALL} and friends, values returned from these accessors carry
+an intended class around and values which can be converted to Lisp values will
+be converted.
+
+
\section{Lisp from Java}
In order to access the Lisp world from Java, one needs to be aware
@@ -941,7 +963,7 @@
suddenly committed that enabled ABCL to be plausibly termed an ANSI
Common Lisp implementation.
-In 2006, the implementation was transferred to the current
+In 2008, the implementation was transferred to the current
maintainers, who have strived to improve its usability as a
contemporary Common Lisp implementation.
More information about the armedbear-cvs
mailing list