---

ixion::javascript Namespace Reference

Compounds
class	ixion::javascript::interpreter
class	ixion::javascript::js_array
class	ixion::javascript::list_scope
class	ixion::javascript::value_with_methods::bound_method
struct	ixion::javascript::context
class	ixion::javascript::value
class	ixion::javascript::value_with_methods
Functions
ref< value >	makeUndefined ()
ref< value >	makeNull ()
ref< value >	makeValue (signed long val)
ref< value >	makeConstant (signed long val)
ref< value >	makeValue (signed int val)
ref< value >	makeConstant (signed int val)
ref< value >	makeValue (unsigned long val)
ref< value >	makeConstant (unsigned long val)
ref< value >	makeValue (unsigned int val)
ref< value >	makeConstant (unsigned int val)
ref< value >	makeValue (double val)
ref< value >	makeConstant (double val)
ref< value >	makeValue (std::string const &val)
ref< value >	makeConstant (std::string const &val)
ref< value >	makeArray (TSize size=0)
ref< value >	makeLValue (ref< value > target)
ref< value >	wrapConstant (ref< value > val)
void	addGlobal (interpreter &ip)
void	addMath (interpreter &ip)
void	addStandardLibrary (interpreter &ip)

---

Detailed Description

This code tries to be an implementation of ECMAScript 4, as available at http://www.mozilla.org/js/language/ Note that ES4 is still in the process of standardization.

It is meant to behave like an ES4 interpreter in strict mode, none of the backward-compatible braindead-isms like newline semicolon insertion and other stuff will ever be implemented.

This is the list of its shortcomings:

• exceptions
• namespaces,packages
• constness
• Number/String constructor and class methods
• real regexp's
• the methods listed in FIXME's (js_library.cc js_value.cc)
• cannot cross-assign predefined methods [won't be]
• Grammatical semicolon insertion [won't be]
• type declaration [won't be]

Be advised that a javascript value that is passed to you through the interpreter, e.g. as a call parameter, may not be of the type that you expect. For example, in "var x = 4; f(x);", what comes in as the parameter x into f is a wrapper value that adds assign()ability to a value that is wrapped inside. The advised solution to get the object that you expect is to call eliminateWrappers() on the potentially wrapped value.

---

Function Documentation

void addGlobal (  interpreter &    ip )

void addMath (  interpreter &    ip )

void addStandardLibrary (  interpreter &    ip )

ref<value> makeArray (  TSize    size = 0 )

ref<value> makeConstant (  std::string const &    val )

ref<value> makeConstant (  double    val )

ref<value> makeConstant (  unsigned int    val )

ref<value> makeConstant (  unsigned long    val )

ref<value> makeConstant (  signed int    val )

ref<value> makeConstant (  signed long    val )

ref<value> makeLValue (  ref< value >    target )

ref<value> makeNull (    )

ref<value> makeUndefined (    )

ref<value> makeValue (  std::string const &    val )

ref<value> makeValue (  double    val )

ref<value> makeValue (  unsigned int    val )

ref<value> makeValue (  unsigned long    val )

ref<value> makeValue (  signed int    val )

ref<value> makeValue (  signed long    val )

ref<value> wrapConstant (  ref< value >    val )

---