Message written at 10 Feb 1999 07:32:55 +0000

Following e-mail exchanges with Nicola and the "Csund-Unix
development" group I though I would seek advice.  There are a
small(ish) number of opcodes which start with i, k or a, and some with
a ga 
.  The list is

        "instr"       "init"    "ihold"         "int"
        "i"           "interp"  "in"            "ins"
        "inh"         "ino"     "igoto"         "icgoto"
        "itablew"     "itablegpw" "itablemix"   "itablecopy"
        "itimek"      "itimes"  "instimek"      "instimes"
        "ilimit"      "ion"     "ioff"          "iondur"
        "iondur2"     "ioutc"   "ioutc14"       "ioutat"
        "ioutpc"      "ioutpat" "imidic14"      "imidic21"
        "ictrl7"      "ictrl14" "ictrl21"       "initc7"
        "initc14"     "initc21" "islider8"      "islider16"
        "islider32"   "islider64" "is16b14"     "is32b14"

        "kgoto"       "kcgoto"   "koutc"        "koutc14"
        "koutpb"      "koutat"   "koutpc"       "koutpat"

        "abs"         "ampdb"    "ampmidi"      "aftouch"
        "adsyn"       "atone"    "areson"       "alpass"
        "atonek"      "aresonk"  "agogobel"     "adsr"

        "gauss"       "gain"

There are some advantages in renaming some or all of these, but there
are longstanding names here.  Does anyone have comments, actual
renaming suggestions, or other help to offer?

Dear John, dear all,

On Wed, 10 Feb 1999 jpff@maths.bath.ac.uk wrote:

> Following e-mail exchanges with Nicola and the "Csund-Unix
> development" group I though I would seek advice.  There are a
> small(ish) number of opcodes which start with i, k or a, and some with
> a ga 
> .  The list is
> 
>         "instr"       "init"    "ihold"         "int"
[etc. etc. follows list - snip]

> There are some advantages in renaming some or all of these, but there
> are longstanding names here.  Does anyone have comments, actual
> renaming suggestions, or other help to offer?

If I may add some other word, I would propose:

1) as things stand, we either have very consolidated symbols which may
   almost be considered 'keywords' (instr, int, etc.) or new names which
   are more or less likely to be used as variable names

2) we should consider renaming the newer ones which are more likely to be
   used as variables (such was the case of 'iwrap'), and keep the other
   ones to avoid further orc breaking

3) maybe we (you :), I would not be able to) could add some clearer error
   message when a variable/opcode conflict occurs so that it is at least
   easier to take care of during orchestra writing

Nicola

P.S. Btw, in the original csound there where some 'w' type variables (the
     spectrum, etc.); do they still exist, thus potentially conflicting
     with the 'wrap' opcode?

------------------------------------------------------------------------
Nicola Bernardini
E-mail: nicb@axnet.it
 
Re graphics: A picture is worth 10K words -- but only those to describe
the picture.  Hardly any sets of 10K words can be adequately described
with pictures.