Well, I think the reason it was put in was to speed up the start time
of csound by not loading any libraries unless an opcode that is found
within it is needed.  I don't know how much time it shaves off though
and have not done any measurements.

The one thing to note is that if the code is left in but we remove the
opcodes.dir, then it'll run without deferring the loading of plugins.
If there was an automated solution that could build the opcodes.dir
automatically, then it might not be any hassle to leave it in.

However, that's adds probably another complication to the build, and
as Michael said, probably just minor gain for a lot of mental
overhead.

Should we do a metric of some sort first before removing in case it
does yield non-negligible speed up, or just go ahead and remove?

steven

On 11/24/06, root <root@codemist.co.uk> wrote:
> I was not award that we had this, and it seems to me like a terrible idea
> -- I almost typed a silly idea.  What is the reason?
> ==John ff
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net