>Dynamic allocation is required for instantiation. That is, special >host calls will be needed to replace the standard ones. Now, is the >host supposed to do this by hiding malloc() etc from the plugin when >it's loaded, or should we use functions with other names? (I'm still >not convinced that loader tricks are the way to go.) This is one of the reasons why I am a C++ fan. Consider how nice it is to be able to say: class Plugin { . . protected: void *malloc (); . . }; class MyPlugin : public Plugin { MyPlugin () { foo = malloc (...); } . . private: void *foo; . . }; Voila - if all plugins were derived from Plugin, we'd instantly have control over all this stuff. Alas, I accept the need for a C API. Sigh. --p
- Re: [linux-audio-dev] Real time plug ins Benno Senoner
- [linux-audio-dev] 0.5.6: change in behav... Fernando Pablo Lopez-Lezcano
- Re: [linux-audio-dev] Real time plug ins James McCartney
- Re: [linux-audio-dev] Real time plug ins Paul Barton-Davis
- Re: [linux-audio-dev] Real time plug... James McCartney
- Re: [linux-audio-dev] Real time ... Juhana Sadeharju
- Re: [linux-audio-dev] Real time ... Paul Barton-Davis
- Re: [linux-audio-dev] Real t... James McCartney
- Re: [linux-audio-dev] Real time plug... David Olofson
- Re: [linux-audio-dev] Real time plug ins David Olofson
- Re: [linux-audio-dev] Real time plug... Paul Barton-Davis
- Re: [linux-audio-dev] Real time ... David Olofson
- RE: [linux-audio-dev] Real time plug ins Richard W.E. Furse
- Re: [linux-audio-dev] Real time plug ins James McCartney
- Re: [linux-audio-dev] Real time plug ins James McCartney