Mercurial > hg > truffle

changeset 22094:0058a9461865

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Truffle/instrumentation: minor Javadoc fixes
author Michael Van De Vanter <michael.van.de.vanter@oracle.com>
date Mon, 17 Aug 2015 15:24:22 -0700
parents 0f0e34039769
children 1e78795e7e6a
files truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/TruffleLanguage.java truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/debug/ExecutionEvent.java truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/vm/TruffleVM.java
diffstat 3 files changed, 12 insertions(+), 12 deletions(-) [+]
line wrap: on
line diff
--- a/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/TruffleLanguage.java	Mon Aug 17 15:24:00 2015 -0700
+++ b/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/TruffleLanguage.java	Mon Aug 17 15:24:22 2015 -0700
@@ -39,12 +39,12 @@
 import java.util.WeakHashMap;
 
 /**
- * An entry point for everyone who wants to implement a Truffle based language. By providing
+ * An entry point for everyone who wants to implement a Truffle based language. By providing an
  * implementation of this type and registering it using {@link Registration} annotation, your
  * language becomes accessible to users of the {@link TruffleVM Truffle virtual machine} - all they
- * will need to do is to include your JAR into their application and all the Truffle goodies (multi
- * language support, multitenant hosting, debugging, etc.) will be made available to them.
- * 
+ * will need to do is to include your JAR into their application and all the Truffle goodies
+ * (multi-language support, multitenant hosting, debugging, etc.) will be made available to them.
+ *
  * @param <C> internal state of the language associated with every thread that is executing program
  *            {@link #parse(com.oracle.truffle.api.source.Source, com.oracle.truffle.api.nodes.Node, java.lang.String...)
  *            parsed} by the language
@@ -99,7 +99,7 @@
      * <em>execution</em>. The returned execution context is completely language specific; it is
      * however expected it will contain reference to here-in provided <code>env</code> and adjust
      * itself according to parameters provided by the <code>env</code> object.
-     * 
+     *
      * @param env the environment the language is supposed to operate in
      * @return internal data of the language in given environment
      */
@@ -179,7 +179,7 @@
      * Allows a language implementor to create a node that can effectively lookup up the context
      * associated with current execution. The context is created by
      * {@link #createContext(com.oracle.truffle.api.TruffleLanguage.Env)} method.
-     * 
+     *
      * @return node to be inserted into program to effectively find out current execution context
      *         for this language
      */
@@ -191,7 +191,7 @@
 
     /**
      * Uses the {@link #createFindContextNode()} node to obtain the current context.
-     * 
+     *
      * @param n the node created by this language's {@link #createFindContextNode()}
      * @return the context created by
      *         {@link #createContext(com.oracle.truffle.api.TruffleLanguage.Env)} method at the
--- a/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/debug/ExecutionEvent.java	Mon Aug 17 15:24:00 2015 -0700
+++ b/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/debug/ExecutionEvent.java	Mon Aug 17 15:24:22 2015 -0700
@@ -34,8 +34,8 @@
  * place to initialize debugger - e.g. set
  * {@link Debugger#setLineBreakpoint(int, com.oracle.truffle.api.source.LineLocation, boolean)
  * breakpoints} or specify to execution should halt on the {@link #prepareStepInto() first possible
- * occurence}. Methods in this event can only be used while the handlers process the event. Then the
- * state of the event becomes invalid and subsequent calls to the event methods yield
+ * occurrence}. Methods in this event can only be used while the handlers process the event. Then
+ * the state of the event becomes invalid and subsequent calls to the event methods yield
  * {@link IllegalStateException}. One can however obtain reference to {@link Debugger} instance and
  * keep it to further manipulate with debugging capabilities of the {@link TruffleVM} when it is
  * running.
@@ -48,7 +48,7 @@
     }
 
     /**
-     * Debugger associated with the execution. This debuger remains valid after the event is
+     * Debugger associated with the execution. This debugger remains valid after the event is
      * processed, it is possible and suggested to keep a reference to it and use it any time later
      * when evaluating sources in the {@link TruffleVM}.
      *
--- a/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/vm/TruffleVM.java	Mon Aug 17 15:24:00 2015 -0700
+++ b/truffle/com.oracle.truffle.api/src/com/oracle/truffle/api/vm/TruffleVM.java	Mon Aug 17 15:24:22 2015 -0700
@@ -47,10 +47,10 @@
  * <p>
  * It would not be correct to think of a {@link TruffleVM} as a runtime for a single Truffle
  * language (Ruby, Python, R, C, JavaScript, etc.) either. {@link TruffleVM} can host as many of
- * Truffle languages as {@link Registration registered on a classpath} of your <em>JVM</em>
+ * Truffle languages as {@link Registration registered on a class path} of your <em>JVM</em>
  * application. {@link TruffleVM} orchestrates these languages, manages exchange of objects and
  * calls among them. While it may happen that there is just one activated language inside of a
- * {@link TruffleVM}, the greatest strength of {@link TruffleVM} is in inter-operability between all
+ * {@link TruffleVM}, the greatest strength of {@link TruffleVM} is in interoperability between all
  * Truffle languages. There is 1:N mapping between {@link TruffleVM} and {@link TruffleLanguage
  * Truffle language implementations}.
  * <p>