| Actually, I would like to be free to use the underscore character in
oopcode names, so I'd rather prefer Istvan style, i.e. using '.' instead
of '_' for the orchestra internal naming issues. I prefer so, because
'.' would never be used as part of a Csound identifier (opcode or variable).
Do you think that this would rise too many troubles in Csound5?
Gab
Matt J. Ingalls wrote:
> istvan had some fix that channed internally all the '_'s
> to '.'s -- for example:
>
> { "oscilv.kk", S(XOSC), 5, "a", "kkio", Foscset, NULL, Fosckk
> },
> { "oscilv.ka", S(XOSC), 5, "a", "kaio", Foscset, NULL, Foscka
> },
> { "oscilv.ak", S(XOSC), 5, "a", "akio", Foscset, NULL, Foscak
> },
> { "oscilv.aa", S(XOSC), 5, "a", "aaio", Foscset, NULL, Foscaa
> }
>
>
>
>
>
>
> On Sat, 3 Jul 2004, gogins@pipeline.com wrote:
>
>
>>This already exists in both FLsetVal_i and FLsetVali forms in Csound 5.
>>
>>----- Original Message -----
>>From: "Art Hunkins"
>>To: "Csound Developers Discussion List"
>>Sent: Thursday, July 01, 2004 6:16 PM
>>Subject: [CSOUND-DEV:4868] The Accursed Underscore
>>
>>
>>
>>>Just a couple of words to add here (following on John):
>>>
>>>Sounds like there are several ways of dealing with this "_" issue. Since
>>
>>you
>>
>>>developers are *doing* it, you guys decide. Of course, that includes just
>>>letting the flogged horse lie!
>>>
>>>My only practical interest is that Csound5 and CsoundAV end up with the
>>
>>same
>>
>>>syntax. I originally proposed changing FLsetVal_i to FLsetVali - just like
>>>Gab (in AV) had changed all the other FLTK opcodes with underscores (AV
>>>currently allows for *either* version). Don't know why he didn't change
>>>FLsetVal_i at the same time, but he didn't. Meanwhile, Luis piped up that
>>>FLsetVal_i was *working* in Csound4, Linux edition.
>>>
>>>I can't imagine that eventually Gab would mind adding FLsetVali as an
>>>alternative format in AV. For my purposes, of course, the main objective
>>
>>is
>>
>>>to have AV and CS5 syntax in harmony!
>>>
>>>Art Hunkins
>>>
>>>To: Csound Developers Discussion List
>>>Subject: [CSOUND-DEV:4857] Re: Latest WinCsound5
>>>From: jpff@codemist.co.uk
>>>Date: Tue, 29 Jun 2004 21:01:59 +0100
>>>As _ is not an allowed symbol in an opcode the -z mechanism knows that
>>>when it reads an _ it has finished the opcode name and only the
>>>arguments differ.
>>> This is amongst the reason I keep says _ in NOT A VALID CHARACTER
>>>IN AN OPCODE. It may work in some cases, but that does not make it
>>>valid. With the mythical new parser this ca (a) be enforced and (b)
>>>relaxed.
>>>
>>>==John ffitch
>>>
>>
>>--------------------------------------------------------------------
>>mail2web - Check your email from the web at
>>http://mail2web.com/ .
>>
>>
>
>
>
--
Gabriel Maldonado
http://csounds.com/maldonado
-- |