Hmm, maybe its related to the non-ASCII-looking characters in your opening block-comment. When I remove all of the characters of that sort from line 28, it seems to work fine in miniAudicle. For some reason it is not apparently necessary to remove any other non-ASCII characters to get it working, like the ones on line 13. Anyways, this seems like an all-too-common "assume everything is 7-bit ASCII" error at some point between where the text is shown in mini and where it is fed into ChucK. Notably it works fine in command line chuck, which I don't think was explicitly mentioned. Also, assuming you are comfortable making your code public, I'm sure the list (and people who come across this thread in the potentially distant future) wouldn't mind seeing your code too, so that the issue is as openly documented as possible. At least keep this in mind for future reference! Additionally, please let me know if I can submit your code to miniAudicle's public issue tracker. Thanks, spencer On Aug 25, 2010, at 3:11 PM, Hans Aberg wrote:

I'll send you my code off the list. When I start the engine, open the file and try to add it, I get the error: [diatonic.ck]:line(1).char(1): syntax error If I remove the initial C comment or put some stuff before it, it is OK.

On 25 Aug 2010, at 21:55, Spencer Salazar wrote:

...

Hans,

Can you provide an example of this, or steps to reproduce the issue? I can't find any new problems here.

One consideration -- miniAudicle's syntax highlighter has some fairly significant shortcomings compared to similar applications (Xcode, Emacs, VS, etc.). Especially with regards to block comments, syntax may not always be highlighted correctly. Fixing this up is on the short term roadmap.

In any case, incorrect syntax highlighting should not change anything about the code that is run on the VM. Even if things are highlighted incorrectly, the code should function equivalently to code run in the chuck command line binary.

spencer

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

If you look back some time ago on this list, I asked if there is a ChucK archive to put it. And I put up a version a year ago - it might be confusing having a number of different versions posted on this list. On 26 Aug 2010, at 00:49, Spencer Salazar wrote:

Hmm, maybe its related to the non-ASCII-looking characters in your opening block-comment. When I remove all of the characters of that sort from line 28, it seems to work fine in miniAudicle. For some reason it is not apparently necessary to remove any other non-ASCII characters to get it working, like the ones on line 13.

Anyways, this seems like an all-too-common "assume everything is 7- bit ASCII" error at some point between where the text is shown in mini and where it is fed into ChucK. Notably it works fine in command line chuck, which I don't think was explicitly mentioned.

Also, assuming you are comfortable making your code public, I'm sure the list (and people who come across this thread in the potentially distant future) wouldn't mind seeing your code too, so that the issue is as openly documented as possible. At least keep this in mind for future reference!

Additionally, please let me know if I can submit your code to miniAudicle's public issue tracker.

Thanks, spencer