I don't really mind excluding nonfunctional APIs from the wrappers. I understand that people are getting itchy to release, and this gets in the way.

If you want to exclude APIs from wrapping, then #ifdef'ing in the Csound API headers is definitely the only way to go.

We also could take a look at the API with a view to rewriting some functions that currently take structs or objects to take elementary data types only, if the struct is not wrapped. If the struct IS wrapped, then it should pass in as a SWIG pointer. Or we could add helper functions to the API.

Also we should try to provide polling alternatives to the callbacks people need. The channel stuff already is there, probably more is already there, but it would be worth checking.

Regards,
Mike

-----Original Message-----
From: Steven Yi 
Sent: Nov 17, 2005 12:54 PM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] more SWIG generated code issues

I'm with Victor.  It was very disappointing last time I tried to use
the API to find exactly what Victor found with the situations with
callbacks and types not supported in the host language.  I'd rather
not see it if it is not usable.  Michael's point of it continuing to
be auto updated still holds.  We also get the additional bonus of
knowing what functions need to have typemaps added by seeing them
#ifdef'd out in csound.h (assuming, all wrappers have typemaps added
uniformly).

steven


On 11/17/05, Victor Lazzarini  wrote:
> I don't think anyone will try to mix SWIG and by hand wrappers. I think we
> should exclude everything that
> does not work at present. If anyone offers to add new typemaps to make
> these things work, fine. I really
> don't like to see an API that only half works. It is better to have a
> limited (in relation to C) API than to have
> something that an unaware user might think works. But that's my opinion. We
> should perhaps have a vote
> to decide on this.
>
> Victor
>
> At 16:10 17/11/2005, you wrote:
> >Excluding APIs is also not so great. It might sound like a good idea, but
> >out of sight, out of mind. Once there is no wrapper, nobody will remember
> >that there could be one, or if they do, they will assume it is not
> >possible with SWIG and go off and do it by hand, and then later on it will
> >break. Reality check: Enough of the API has been working through Python
> >and Java to use Csound from those languages for several years now,
> >automatically tracking changes, with almost no effort expended.
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net