Hallöchen!

Meanwhile, this thread was cited elsewhere, which thwarts my
original intention of ignoring it.

T. Modes writes:

> [...]
>
> The cause for this change is the "instability" of the lensfun
> library. The API is in continuous flow, features are added,
> renamed and maybe deleted.  And also the behaviour of some
> functions changes between different releases, and this without
> hint in the release notes or documentation. (For a developer this
> is more difficult to debug. You have to check the return values of
> each lensfun function, and this for each release.)  For a library
> which is mainly used by other programs (and rarely stand alone) I
> find is very strange, but this is only my opinion.  I don't have
> the time to change Hugins code for each lensfun release, otherwise
> the lensfun library does not work correctly.

The lensfun library has a stable and well-documented API.  If we
make changes, we follow the established procedures of obsolescence.
And even that has not been necessary so far.  Moreover, we address
bugs very quickly.

Other programs like Darktable, Digikam, UFRaw, and rawstudio use
lensfun successfully, and never have complained about lensfun being
a moving target.  So, for the sake of fairness to a fellow open
source project, please do not post such discrediting and vague
statements without evidence.

Tschö,
Torsten.

-- 
Torsten Bronger    Jabber ID: torsten.bron...@jabber.rwth-aachen.de
                                  or http://bronger-jmp.appspot.com

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/87egplhd09.fsf%40physik.rwth-aachen.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to