On Wed, Apr 26, 2006 at 05:48:32PM +0100, tom christie wrote:
> > 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.
the only situation it can cause a segfault is where its mangled in a
somehow still structurally and syntaxically correct way (too unlikly to be
worth considering) or if the host pushes on without enough information.
The point I was making is that you will get segfaults if you try to us the
struct without the data, even if you know the version number, so dont.
> 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.
Sure, but its easier to version the struct in the data.
- Steve
Received on Thu Apr 27 00:15:26 2006
This archive was generated by hypermail 2.1.8 : Thu Apr 27 2006 - 00:15:26 EEST