From: Kenneth J. Davis (jeremyd@computer.org)
Date: Wed Oct 22 2003 - 10:43:50 EDT
On 22 Oct 2003 15:43:14 +0200 Marc Maurer <j.m.maurer@student.utwente.nl> wrote:
MM> > succeed. If a user needs to support these image file formats, said
MM> > user should install the plugins! Otherwise why have them as a
MM> plugin?
MM>
MM> To keep our core clean.
MM>
MM> Marc
MM>
MM>
Our core can be just as clean without them being a plugin, for
example consider the work for incorporating the importer/exporters
on platforms that do not support plugins. If an importer/exporter
is required to complete a build, it is required, having it split
into an executable and shared object makes little difference than
being in a single executable if the code is nearly identical and
the dependencies are the same. [Yes in theory, having part of
the code in a shared object does allow for upgrades, but at the
moment we only release plugins at the same time as we release
complete builds, and many updates to our plugins are to take
advantage of, or changes because of, features added/changed in the
rest of our code, so that argument does not yet apply. Arguably,
until we have a stable importer/exporter ABI, it simplifies
matters to have a monolithic build.]
Jeremy
This archive was generated by hypermail 2.1.4 : Wed Oct 22 2003 - 10:45:04 EDT