> That's somewhat like saying a corrupt binary
> should never cause a segfault...
No, not at all.
The data file is accessed as an input stream (to the host / LADSPA library).
It's fine for a bad data file to cause the library to fail to be able
to load it, or to load it and produce unexpected output, but it should
*never* cause it to segfault.
> No-ones seriously interested in guarding against the caes
> where the .so is corrupt.
Agreed, and neither am I.
All I'm saying is that if the discovery function may potentially
return differing structs from one LADSPA version to another, then it
ought also provide a mechanism of determining exactly which struct it
is returning.
If it does that, then the worst that can ever happen is that the
binary is accessed with duff input (no segfaulting).
Okay, I really will shut it now, I begin to suspect I'm labouring the point :)
t.
Received on Thu Apr 27 00:15:24 2006
This archive was generated by hypermail 2.1.8 : Thu Apr 27 2006 - 00:15:24 EEST