On Thursday 22 December 2005 09:08, jpff@codemist.co.uk wrote:

> I realise that I am extreme on this, but good code should not generate
> compiler errors or warnings.  Having just recompiled everything I see
> the following messages.  Many in Loris, but way too many in interfaces

The interfaces (*_wrap.cc) are not written by anyone, they are
automatically generated by SWIG, so the warnings cannot really
be fixed there, other than hoping that future releases of SWIG
will emit cleaner code. Loris is not part of the Csound sources,
and as such is not maintained by Csound developers. The Python
opcodes are also automatically generated, and some of the warnings
are in the Python headers (if compiling with -pedantic).

The only part where there are many warnings that can be actually
fixed (i.e. neither machine generated nor third party code) is
CsoundVST. On the other hand, it also seems to have bugs in FLTK
threading which may be a more important issue than the warnings.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net