On Friday 09 December 2005 15:38, Michael Gogins wrote:

> I don't think WINE is guaranteed to be a fair test. Only testing on actual
> Windows can definitively answer this question.

Well, I will do that too, soon.

> Why do you want to remove the "virtual" declaration, anyway?
>
> In addition to making sure things work on Windows, it also allows the
> methods to be overridden in derived classes. This could have definite
> applications. In fact, I am considering creating default callback handler
> virtual methods that normally just forward to the existing callbacks, but
> can be overridden in classes derived in Python or Java. This would provide
> the simplest method of implementing callbacks in the interface languages,
> at least where SWIG has "directors".

I do not want to remove 'virtual' from the Csound class (perhaps allow
for disabling it, but surely not by default), as I already know your
reasons for using it. I just do not like the idea of it being required
everywhere, even in simple classes, and methods that are only used from
SWIG but not C++. Also, conditionally compiling the message buffer methods
will make the virtual table different if those are made virtual; this may
or may not be a problem, but perhaps that interface could just be removed
as it is very ugly and limited anyway compared to having callbacks.


-------------------------------------------------------
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