Yes. A bit of a shame that JavaScript is THE language for
web-browsers. Hence my focus on that. Some sort of Python would have
been better IMHO.
>
> The bindings (with the exception of python and c++) have a rather
> clunky syntax in this first release - but this this will be solved
> very shortly. Mostly the problem is that native language strings and
> variables cannot be supplied as the arguments of exodus functions.
> Currently you have to pass exodus variables as exodus function
> arguments.
>
> I will be making sure that, to the degree possible in each language,
> that exodus variables and functions work seamlessly with native
> variables and functions.
>
> I will also be doing my best in each language to ensure that built in
> operators work in the pick mentality with . Above all this means that a
> +b will perform mathematical function always and throw "non-numeric"
> runtime error if necessary. I will be hijacking the ^ operator where
> possible to perform concatenation.
Sounds like a good plan.
>
> I believe there is a slowly growing acceptance that overloading
> operators (famously "+" to perform concatenation) was a disaster in
> dynamically typed languages. python is one of the worst with its
> concept that a*b can mean string replication IF "a" happens at runtime
> to contain a string and "b" contains a number.
Exactly. Drives me nuts! ;-)
Ashley
--
You received this message because you are subscribed to the Google Groups "Exodus Users" group.
To post to this group, send email to exodus...@googlegroups.com.
To unsubscribe from this group, send email to exodus-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/exodus-users?hl=en.