If kT[] = [1,2,3,4] is not possible, what about the C syntax?  kT[] = {1,2,3,4} , a 2D version could also be like {{1,2},{3,4}}

-- 
Edward Costello


On Friday 31 May 2013 at 11:04, jpff@cs.bath.ac.uk wrote:

Two questions that we thought might be good to seek the community views.

1: Initialisation of arrays.

We now have statements like
kT[] = fillarray(1,2,3,4)
working. Some concern was expressed about the long-windedness on this.
It has been suggested that we use the simpler/shorter
kT[] = array(1,2,3,4)
or we could seek some other syntax. As far as we can tell the form
kT[] = [1,2,3,4]
is problematic, but we could (for effort) introduce something like
kT[] = '[1,2,3,4]
but is it worth it and would that be clear anyway?

No promises as to what we eventually do but what would be best for users?


2: Strings in Scores

The question relates to escaped characters. Currently the string

"abc\n"

is stored as 5 characters. If it is used in an instrument to print then
the printkS or hatever interprets the \n as a newline.

The alternative is to store this as 4 characters and do the interpretation
of escapes at read time. The down side is that to print a \ character
this way would require 4 \s in the score (that is "\\\\"). However then "
could be included in a string. It is unclear to me which is best.

Any thoughts?

==John ff


------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel