Hi all,

I started getting back into csound5 and thought I'd ask:

-Any objections to removing 'makefile' from the Opcodes directory?  This
interferes with the 'Makefile' that is generated with configure

-a while ago i asked about statements that were generated with csound5
that looked like

42005342 <- 42530042

I remember John was in the middle of using these for testing some byte
reversal code. I've commented them from my InOut/aiff.c file and was
wondering if anyone mind if I check in my aiff.c

-a couple things about the zak stuff that was moved to cglob.  first
thing is that the cvs has:

#define zkstart cglob.zastart
#define zastart cglob.zastart
#define zklast  cglob.zalast
#define zalast  cglob.zalast

which I think should be:

#define zkstart cglob.zkstart
#define zastart cglob.zastart
#define zklast  cglob.zklast
#define zalast  cglob.zalast

if so, I'll check that in.  Also, there's something funny going on with
trying to compile widgets.cpp in regards to the this stuff, as somehow
zkstart is ending up being defined as a long somewhere before it gets
defined as a MYFLT.  for the time being I'm commenting that section of
code out in widgets.cpp (in the fl_slider_bank function, around line
2773).  I'll look into that later, but thought I'd mention it.


-I noticed that csoundAppendOpcode in jpff_glue.c is currently:

printf("DO NOT USE THIS INTERFACE\n");
    return -1;

so I was wondering if dynamically loaded opcodes is working, and if so,
where the function is for that. (I was looking for what directory
csound5 is looking in for it's dynamically loaded opcodes, as I wanted
to see if the shared objects from the Opcodes dir would work).  


Thanks for any replies!
steven