[Digikam-devel] Re: libkdcraw from graphics gsoc-branch

["Jens Müller"]

> > The main problem is about ABI-compability. You extend decoding
> structures to
> > fetch new libraw parameters. But here comes the scenario: If someone
> build
> > digikam 1.6 and link it against libkdcraw from KDE 4.6 and then upgrade
> to KDE
> > 4.7 the application will crash I think. Ugly, but the right way will be
> a
> > duplicate of the structure and the calling method. Am I right? Marcel,
> what do
> > you think?
> 
> this is why we have ABI id and API id.
> 
> Note: The BC is broken if you remove API, not when you add new one...
> 
> Marcel ?
> 

Please correct me if I'm wrong. If the structure is used as a in parameter at library side there should be a problem. The application linked against old lib will allocate a structure in size of the old one. The new library with extended structure will parse the new size. So the there is a out of struture memory call at some place?

Jens

-- 
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail