But [array] provides array ranges, and many other languages provide iterators over array slices, with easy syntax for the whole array. I suppose it doesn't matter that much here because [expr] is kind of its own animal and doesn't really need to conform to [array]'s design.
On Sun, Feb 7, 2016 at 10:45 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
Array.foreach in Javascript runs over the whole array. Just as [list-drip] necessarily drips the entire list.
-Jonathan
On Sunday, February 7, 2016 12:23 AM, Matt Barber brbrofsvl@gmail.com wrote:
Any iterator should be over a range, not the whole array.
On Sat, Feb 6, 2016 at 11:52 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Also-- since you have assignment operator now, would it make sense to have an iterator function for garrays?
Something like: iterate(array_name, expression), where expression is evaluated for each element of the array. Maybe an i() function to get the iteration number.
-Jonathan
On Saturday, February 6, 2016 10:48 AM, Jonathan Wilkes < jancsika@yahoo.com> wrote:
Also, since you mentioned documentation: https://github.com/pd-l2ork/pd/blob/master/doc/pddp/expr-help.pd https://github.com/pd-l2ork/pd/blob/master/doc/pddp/expr%7E-help.pd https://github.com/pd-l2ork/pd/blob/master/doc/pddp/fexpr%7E-help.pd
https://github.com/pd-l2ork/pd/blob/master/doc/pddp/all_about_expr_and_value...
https://github.com/pd-l2ork/pd/blob/master/doc/pddp/all_about_expr_functions... https://github.com/pd-l2ork/pd/blob/master/doc/pddp/all_about_expr_if.pd
https://github.com/pd-l2ork/pd/blob/master/doc/pddp/all_about_expr_multiline...
-Jonathan
On Friday, February 5, 2016 8:45 PM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Sounds great!
On Friday, February 5, 2016 8:37 PM, Shahrokh Yadegari sdy@ucsd.edu wrote:
Dear All,
Attached is a pre-release of Expr 0.5 compiled for Mac os x (compiled on 10.9) and Linux (compiled on an older Cent OS). I have also attached Alexandre's big pd patch which listed the issues, with my comments.
Hopefully I have addressed most of the issues that were brought up and now I am working on a more complete documentation of Expr objects. One open issue is that expr still supports no more than 10 expressions.
I have provided a mechanism for local variables and abstraction substitutions ($0 and $1, $2, etc.) to work. Also, one hopefully useful new feature in V0.5 is the assign '=' operator. Now you can use expr to assign to "value"s and into arrays. So if you have a variable called 'count'
"value count"
"expr count = count + 1"
will implement a counter, raising the value of count with every "bang"
You can also change values of arrays through the usual syntax.
"expr array1[5] = $f1"
will set the sixth value (counting zero based) of the array "array1" to the incoming float value on inlet 1.
I will write a more informative and comprehensive release notes along with the documentation when I pass the sources to Miller. However, I have made a few changes to the parser and I am looking for alpha-testers who can run the code and let me know if any bugs are found, specially in parsing of complex expressions.
I look forward to hearing from whoever uses these objects. Please let me know if you find any bugs. (NOTE: you need to create the links for expr and fexpr~ to get the new version for those as well.)
cheers, Shahrokh
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list