User Tools

Site Tools


at:tutorial:symbiosis

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
at:tutorial:symbiosis [2009/04/23 09:24]
tvcutsem
at:tutorial:symbiosis [2013/05/17 20:25] (current)
tvcutsem updated
Line 53: Line 53:
  
 <note> <note>
-If you want to load your own Java class make sure that the .class file is in the classpath of the JVM running AmbientTalk. By default, the iat script puts the atdirectory of the AmbientTalk distribution in the classpath+If you want to load your own Java class make sure that the .class file is in the classpath of the JVM running AmbientTalk. By default, the iat script adds the standard $CLASSPATH classpath.  
 +</note> 
 + 
 +<note> 
 +Please do not name your own Java packages starting with a capital letter. Otherwise, AmbientTalk will confuse the package with a Java class
 </note> </note>
  
Line 81: Line 85:
 >>nil >>nil
 >aVector >aVector
->><java:[1, 2, 3, 4, 5, 6, 7, 8, 9]>+>><java:[1, 2, 3, 4, 5, 6, 7, 8, 9, 10]>
 </code> </code>
  
Line 175: Line 179:
 >>42 >>42
 </code> </code>
 +
  
 ==== Starting an AmbientTalk interpreter from Java ==== ==== Starting an AmbientTalk interpreter from Java ====
Line 216: Line 221:
  
 <note> <note>
-When starting an AmbientTalk virtual machine from a Java application, the resulting system is inherently multithreaded. The wrappers created by the ''evalAndWrap'' method will ensure that the Java code cannot break the concurrency properties of AmbientTalk. Moreover, by default this wrapper will ensure that the Java thread waits for the result of evaluating the AmbientTalk code which prevents concurrent access on possible Java objects used by the evaluated code. For more detailed information on this topic we refer to our [[ftp://prog.vub.ac.be/tech_report/2007/vub-prog-tr-07-15.pdf|ICDL2007 paper]].+When starting an AmbientTalk virtual machine from a Java application, the resulting system is inherently multithreaded. The wrappers created by the ''evalAndWrap'' method will ensure that the Java code cannot break the concurrency properties of AmbientTalk. Moreover, by default this wrapper will ensure that the Java thread waits for the result of evaluating the AmbientTalk code which prevents concurrent access on possible Java objects used by the evaluated code. For more detailed information on this topic we refer to our [[http://soft.vub.ac.be/Publications/2007/vub-prog-tr-07-15.pdf|ICDL2007 paper]].
 </note> </note>
at/tutorial/symbiosis.1240471468.txt.gz · Last modified: 2009/11/30 17:00 (external edit)