Hi all,

Csound5 cvs has header files for opcode plugins in the H directory (i.e.
Opcodes/babo.c and H/babo.h) and it seemed to me that the headers for
the opcode plugins should be moved into the Opcodes dir, to help clarify
what's internal to the csound engine black box and what isn't.  This
isn't a big deal to me either way, but something I thought would help
tidy things up.  

Any objections to me moving them?

Thanks,
steven

OK by me.  Are you suggesting babo.h in same directory as babo.c, or a 
firectory for plugin headers or what?  Like analysis. Do not understand 
the synthesis.
==John

Yes, I was thinking of moving .h files in the same directory as their .c
counterparts (so into the Opcodes directory).  There aren't too many
files in the Opcodes dir that it would be cluttered, IMO. 

steven


On Tue, 2003-11-18 at 23:54, John ffitch wrote:
> OK by me.  Are you suggesting babo.h in same directory as babo.c, or a 
> firectory for plugin headers or what?  Like analysis. Do not understand 
> the synthesis.
> ==John
> 
> 

That is OK my me.  Did consider that but went for the more easily scripted 
chage -- laziness I guess
==John

Probably not laziness: I've run into a few things, so it's taken me some
time to move the headers.  The things I've run into:

========================================================

[extraneous #includes in entry2.c ]

I commented these out; seemed like leftovers from another time


[duplicates of .c files in Opcodes and OOps]

Not sure which files need to be where.  Duplicates I've found are:

ugens6.c
ugens7.c
ugens9.c


[some headers included by other files in OOps]

i.e. pitch.h is being used by OOps/pitch0.c and Opcodes/pitch.c

========================================================

I moved all of the headers I found referenced in the .c files in the
Opcodes dir and then repeatedly tried compiling csound and moving back
headers until compilation ran without errors.  I'm reasonably confident
I moved only headers safe to move.

Also, H/OpcLoad.h and H/foo.h seem like candidates to be deleted. 
OpcLoad.h is dated 1997 and foo.h has no license information and looks
to be there as an example struct to use for opcode developers.

Thanks,
steven


On Wed, 2003-11-19 at 00:36, John ffitch wrote:
> That is OK my me.  Did consider that but went for the more easily scripted 
> chage -- laziness I guess
> ==John
> 
> 

Some of those things are not a surprise; some need thought.  Will look at 
it today and comment
==John