I recall muttering darkly about gogobel a while back! If I saw 'lpassn'
as an opcode, my immediate instinct would be to assume it referred to a
low-pass filter of some kind.

I suppose, if we were all to start over, we would use uppercase
characters for the rate signifiers, so we could have variables such as
Asomething, Ksomething and so on, and thus keep allpassn and agogbel et
al.  in the idiomatic form that pleases the eye and calms the mind.



Richard Dobson
 

pete moss wrote:
> 
> sorry, i need to vent here.
> 
> i think the whole idea of avoiding an initial a, k, or i in an opcode
> name is a silly thing in some cases.  granted, there doesnt need to be
> ipow, kpow, and apow if there can just be pow.  but alpassn -> lpassn ?
> why?  i also dont agree that agogobel should have been changed to
> gogobel.  some opcodes should be left alone.  starting with a, k or i
> shouldnt be banned if it makes sense!  alpassn makes some sense whereas
> lpassn doesnt.  besides, a good programmer should be able to avoid using
> reserved keywords in code.  i dont write code in c and use variables
> named if, asm, or static.  i think we have gone too far in this not
> polluting the variable namespace issue.  a few things need to be changed
> back to what they were.
> 
> :P
> 
> > You probably know that the initial letter should usually not be
> > an a, k or i, as this disrupts the orchestra variable namespace.

-- 
Test your DAW with my Soundcard Attrition Page!
http://wkweb5.cableinet.co.uk/rwd (LU: 23rd August 1999)