String indexing

[brad]

Will this work for string indexing? Worked well for me. I was able to loop through a string using len() and echo individual characters accessed using [i].

[kintel]

To elaborate on tests:
I can do this myself, but it would be good training in writing patches which can be merged directly :)

A successful test of a feature like this would be to write an .scad script stress testing of the feature with different legal, illegal and border-line cases, then echo()'ing the results. The test file would go into tests/scad/misc/<mytest.scad>, and the test should be added to the echotest in tests/CMakeLists.txt.
Now, in tests:
$ cmake .
$ make
$ ctest -R echotest_mytest
[ should fail ]
$ cat echotest-output/echotest_mytest.txt
[ manually verify that the output is correct and fix any issues until it is ok ]
$ TEST_GENERATE=1 ctest -R echotest_mytest
[ should pass ]
$ ctest -R echotest_mytest
[ should pass ]
$ git add regression/echotest/mytest-expected.txt

[brad]

Added some tests. Thanks for the detailed write up on the test framework, Marius. I was unable to "make all" (cgaltest complain about many undefined gl* references) but I did "make echotest" and was able to test that way.
I noticed one strange thing, but maybe it's by design. List indexing (vector and string) will accept any type of number and cast it to int. For example echo([0, 1][1.5]) prints "1". The cast rounds down to the nearest int. Is that by design?

[kintel]

Thanks!
OpenSCAD doesn't distinguish between floats and ints. Internally everything is a double. This may change, so it's good to have a test for it.