Hmm... well, my first inclination was to use dots to manage channel names in way like namespaces are done for java and python package naming. If it's not too much trouble, I'd appreciate the dot being added as a valid character. Thanks! steven On 1/11/06, Istvan Varga wrote: > On Wednesday 11 January 2006 05:51, Steven Yi wrote: > > > Just tried this: > > > > chnget "table.sine" > > > > and I get an invalid channel name. If i use: > > > > chnget "table_sine" > > > > things are fine. Is this a bug? I can imagine it being somehow > > related to the parser I guess using periods for overloaded opcodes. > > Is this already documented (I checked but didn't find anything > > mentioned) > > This has nothing to do with the parser. Channel names must consist > of letters, digits, and the underscore character, and the first > character should be a letter. More characters could be allowed if > that is found to be useful, though. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Csound-devel mailing list > Csound-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/csound-devel > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net