On Sat, Oct 31, 2009 at 1:40 PM, David Robillard <[email protected]> wrote: > On Sat, 2009-10-31 at 17:35 +0100, [email protected] wrote: >> On Sat, Oct 31, 2009 at 12:08:54PM -0400, David Robillard wrote: >> >> > ... This is exactly >> > like blaming the shared library mechanism for the fact that there's no >> > open source shared library to do realtime granular resynthesis, or >> > whatever. >> >> It's very different. If I want to write a library to do >> realtime granular synthesis I don't have to extend the >> shared library mechanism first, or write a new dynamic >> linker. > > You don't need to extend the extension mechanism first (I don't even > know what this means...) or write a new host either. > > Shared library, you get a thing by filename, it has code in it. > Extension, you get a thing by URI, it has code in it. > > It is not "very different" at all.
that's just one side of the equation. having found the thing, what gets done with it? there are two things with a shared library: * run time linker gets it all nicely set up in the address space of the process * parts of the app call functions in the library API to get things done with an LV2 extension, what are the analogies? _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
