Hello concerned coders,


Matt J. Ingalls <
} > With a little extra work I also compiled the perf 68K and FAT 
} 	very cool! send the changes/binaries!! 

Sure thing - I wouldn't like to have to do that again. They 
should be on your desk tomorrow or Sunday (my server's just 
upgraded and access has been sporadic). I also made a start on 
another sub-project as a CFM thing. It compiled but would not 
make. I'll try to get it working before I send things over as 
it's probably what the 68K users would want.


} > However, in order to bring the code up to ANSI strict standards 
} > and avail myself of CodeWarrior's (minimal) error checking 
} > facilities, I've had to create several hundred prototypes and 
} > "fix" hundreds of errors (like unused arguments and variables).

} yuck - a few months ago i made some changes to canonical sources
} to remove some of the compiler warnings, but the unused arguments and
} "several hundred" prtotypes was so much i just turned the options off
} in the compiler prefs (i think i put that in the README)

It seems to me that it's only an advantage to get all the code 
to go though as much error checking as possible - even so it's 
been pointed out to me that CodeWarrior won't find unused 
functions or give warnings on variables that are unused but 
have been initialized (as when the C++ compiler is turned on 
and requires initialized variables).


} im about to merge the 3.494 sources -- maybe its about time to remove
} mills as ftp (since its currently messed up anyway) and get ALL the mac
} stuff up on the bath site!

I must have tried every link to the sources I could find on 
 but still didn't come up with the one you popped over 
so maybe that would be a good idea.



John F. Fitch <
} The Cspoudn sources are ANSI. Thre are a few compilers who 
} misunderstand the Standard, and demand prototypes which are not 
} required. The declaration of a function includes teh prototype, 
} but some dumb compilers, and they seem to be on Macs, seem to 
} require

} void foo(int);
} void foo(int x) {
} ...
} }

Platform bashing is hardly the point John. At least Matt has 
picked up on the fact that I'm trying to help you become the 
maintainer of the tightest code on the block. If all goes well 
with my changes on the Mac side of things I'd be pleased if 
you'd run them through your compilers and point out if there's 
any adaption which doesn't come through. I've made all 
significant changes with a conditional so you could switch it 
off or on to suit. Also I'd appreciate your advice on whether 
or not it would be better to use the 'extern' keyword rather 
than stuffing the commonly used functions into the prototyp.h 
file as I've done now.


} The system compiles with zero warnings on PCs, UNIX, gcc, etc etc

You might have mis-read my previous post. It started off like:

> The 3.493PPCsources project for PPC compiled straight out of 
> the box. Marvellous! Thanks to the many contributors for making 
> this possible.


Mike Berry <
} On the CodeWarrior compilers (which are the only Mac ones worth 
} speaking of) there is an option in the C/C++ preferences called 
} "Require Function Prototypes." Simply turn this off, and all of 
} those prototype warning go away.

One of the things I'm trying to do is coordinate the Csound 
code hunk with another environment. This requires all the error 
checking that CW provides except for inplicit arithmetic 
conversions.


Thanks for you various responses,


Philip


Philip Aker
Composer, Pianist, Finale Plugins

Suite 13
1405 West 11 Avenue
Vancouver BC
Canada V6H 1K9

philip@vcn.bc.ca