`instxtcount' and `optxtsize' are there from the first csound5 commit
but not used. I think that the follow chunk is removable in csound_orc_compile.c:1371

    ip = &(csound->instxtanchor);               /* set the OPARMS values */
    instxtcount = optxtcount = 0;
    while ((ip = ip->nxtinstxt) != NULL) {
      instxtcount += 1;
      optxtcount += ip->optxtcount;
    }
    //    csound->instxtcount = instxtcount;
    csound->optxtsize = instxtcount * sizeof(INSTRTXT)
                        + optxtcount * sizeof(OPTXT);


`instxtcount' removable in csound_orc_compile.c:1044

`instxtcount' and `optxtsize' removable in csoundCore.h:1446 and csound.c:720.

`tran_nchnlsi' is new in git-014510b46a9f479190d8e (More spin.spout separation).
Only association without use and I think that it is removable.

`sstrlen0', lengths for the extra strings, is new in git-f21a28f700eb8f3a0c455a88444
(revised GENsone). Before it was

  int *sstrlen0[3];

then it becomes

  int sstrlen0[3];

It is unused from the origins, so it is removable.

I think that gbl{a,k,s}count variables was useful with the old parser
because used in `oload' and `otran' functions (also `gbloffndx'). Only in the
`csound_orc_compile' function it doesn't make sense.

Idem for `gblnxt{a,s,p,k}cnt', in `otran' and `gblnamset' functions.
No sense only in `csound_orc_compile' func.

The todo is to update.

tito

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net