On Jul 29, 2006, at 9:29 AM, Lars Luthman wrote:
I don't think there is a way to actually prevent someone else from
writing a generic implementation or a different specialisation in
their
own source, but if they try that they should _really_ know what
they are
doing.
I've heard that a mec
Erik de Castro Lopo wrote:
> Erik de Castro Lopo wrote:
>
> > Hi all,
> >
> > Thanks to suggestions from people here I now have a relatively
> > complete C++ wrapper for libsndfile:
> >
> > http://www.mega-nerd.com/tmp/sndfile.hh
An another update incorporating a number of suggestions from
Erik de Castro Lopo wrote:
> Hi all,
>
> Thanks to suggestions from people here I now have a relatively
> complete C++ wrapper for libsndfile:
>
> http://www.mega-nerd.com/tmp/sndfile.hh
I've updated this with the following:
- Templatize the read/write/readf/writef methods.
- Stop (pot
On Sat, 2006-07-29 at 23:14 +1000, Erik de Castro Lopo wrote:
> Lars Luthman wrote:
>
> > The 4 different overloaded versions of the read, readf, write, and
> > writef functions will cause ambiguities that will force you to cast them
> > to their respective types in order to use pointers to them,
Lars Luthman wrote:
> The 4 different overloaded versions of the read, readf, write, and
> writef functions will cause ambiguities that will force you to cast them
> to their respective types in order to use pointers to them, for example
> in functors (e.g. a sigc++ slot), like this:
>
> mem_fu
On Sat, 2006-07-29 at 21:31 +1000, Erik de Castro Lopo wrote:
> Hi all,
>
> Thanks to suggestions from people here I now have a relatively
> complete C++ wrapper for libsndfile:
>
> http://www.mega-nerd.com/tmp/sndfile.hh
>
> There is also a pre-release of libsndfile which includes a
> test
Hi all,
Thanks to suggestions from people here I now have a relatively
complete C++ wrapper for libsndfile:
http://www.mega-nerd.com/tmp/sndfile.hh
There is also a pre-release of libsndfile which includes a
test for this wrapper:
http://www.mega-nerd.com/tmp/libsndfile-1.0.17pre7.tar.gz
