>However, if I understand the model correctly, there is nothing preventing >a LAAGA application from scribbing on data malloc'd by another LAAGA app >in the single thread model, isn't this likly to be a problem? It reasonable >to shout at people who write buggy, simple LADSPA plugins, but full on HD >recorders (for example) are a damn sight more complicated and could easily >tread on each others toes. Not to mention the extra complications for >debugging. Yes, these are both real issues. However, if and when the single-thread model is accepted, they are just part of the unpleasant facts of life. --p
- [linux-audio-dev] high level laaga Paul Davis
- [linux-audio-dev] Re: high level laaga Abramo Bagnara
- Re: [linux-audio-dev] Re: high level laaga Steve Harris
- Re: [linux-audio-dev] Re: high level laaga Paul Davis
- Re: [linux-audio-dev] Re: high level laaga Steve Harris
- Re: [linux-audio-dev] Re: high level ... Paul Davis
- Re: [linux-audio-dev] Re: high le... Steve Harris
- Re: [linux-audio-dev] Re: high level ... Steve Harris
- Re: [linux-audio-dev] Re: high le... Paul Davis
- Re: [linux-audio-dev] Re: hig... Steve Harris
- Re: [linux-audio-dev] Re: high level ... Paul Davis
- Re: [linux-audio-dev] Re: high le... Steve Harris
- Re: [linux-audio-dev] Re: hig... Steve Harris
- Re: [linux-audio-dev] Re: hig... Paul Davis
