Release Candidate 3

This is a minor update of Release Candidate 2.

o.overview should be fixed.

Release Candidate 2

Fixed blobs, miscellaneous bugfixes.

Persistent storage in o.compose is not a part of this release - but it has been mostly sorted, and only needs some testing before being added.

Release Candidate for o.io and Oscuino

This release compounds all of our bugfixes made during MMJSS and in the subsequent week. Please note that for future-proofing your lambdas, you will now need to call readstring on the lambda string expression. Examples in the repo have been updated appropriately.

Beta

v1.0.0b

orange

o.change has outlets swapped

v0.10.9

Merge branch 'master' of https://github.com/CNMAT/CNMAT-odot

Beta for MMJSS

v0.10.8

Merge branch 'master' of https://github.com/CNMAT/CNMAT-odot

Nightly build

A number of bugfixes, notably, the o.expr parser will fail if there is a comma after the final expression. I.e.,

/foo = 10,
/bar = 20,

will fail due to the final comma---it needs to be

/foo = 10,
/bar = 20

New lambda syntax

The syntax for lambda has changed from

lambda(a, b, c){expr1;, expr2;, exprn;}

to

lambda([a, b, c], expr1, expr2, exprn)

That is to say, the arguments to the lambda must be enclosed in a list and passed as the first arguments, and the expressions are comma separated arguments to the lambda form, not semicolon terminated.

Maintenance release

This release contains a number of bugfixes including:

---o.validate catches packets with bogus lengths
---?? and ??= have high precedence
---[] == list()
---removed error reporting from o.slip.*

Merge of new syntax

v0.10.0

moved a couple minor changes to o.message/compose/display from backpo…