Difference between revisions of "Calico Boo"

From IPRE Wiki
Jump to: navigation, search
 
Line 1: Line 1:
Calico (so far) uses the standard version of Boo, so any regular Boo program should work without issue.
+
Calico (so far) uses a standard, if not older, version of Boo, so any regular Boo program should work without issue.  
 
+
Boo is not a language based on the Dynamic Language Runtime (DLR), so that there are not known means to call Python or Ruby programs from Boo. Also, the DLR environment is not currently available to Boo. We are currently looking into these limitations.
+
  
 
To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example:
 
To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example:
Line 10: Line 8:
 
= Introduction to Boo =
 
= Introduction to Boo =
  
Please see:
+
For an introduction to Boo, please see:
  
 
http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf
 
http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf

Latest revision as of 10:26, 19 April 2014

Calico (so far) uses a standard, if not older, version of Boo, so any regular Boo program should work without issue.

To use a Calico module, one needs to import it (which brings the module's items into the current namespace, unlike Python which keeps the names in the Myro module namespace). Also, one must provide all of the arguments for each parameter. For example:

boo---> import Myro
boo---> init("COM5", 38400)

Introduction to Boo

For an introduction to Boo, please see:

http://jbryankelly.files.wordpress.com/2012/07/thinksciboorev2_hb.pdf