# LibraryReExportIsNPComplete

### From APIDesign

(→Conclusion) |
(→Conclusion) |
||

Line 82: | Line 82: | ||

If there is a [[Module system|repository of modules]] in various (incompatible) versions, with mutual dependencies and re-export of their [[API]]s, then deciding whether some of them can be enabled is [[wikipedia::NP-complete|NP-complete]] problem. | If there is a [[Module system|repository of modules]] in various (incompatible) versions, with mutual dependencies and re-export of their [[API]]s, then deciding whether some of them can be enabled is [[wikipedia::NP-complete|NP-complete]] problem. | ||

+ | |||

+ | As [[wikipedia::NP-complete|NP-complete]] problems are hard to solve, it is usually our best desire to avoid them in real life situations. What does that mean in case one decides to practise [[DistributedDevelopment]] (and it is [[TheAPIBook|inevitable that software for 21st century needs]] this development style)? If you want to avoid headaches with finding the right configuration of various version of the libraries that allows to execute them together, then stick with following simple rules. | ||

+ | |||

+ | ==== Be Compatible! ==== | ||

+ | |||

+ | If you develop your own libraries in [[BackwardCompatibility|backward compatible]] way, you can always select the most recent version of each library. That is the configuration you are looking for. It is easy to find (obviously) and also it is the most desirable, as it delivers the most modern features and bugfixes that users of such libraries want. | ||

+ | |||

+ | ==== Reuse with Care! ==== | ||

+ | |||

+ | If you happen to reuse libraries (and you should because reuse lowers [[Time to Market]], just like it did for me when publishing my first [[First Amoeba Video|animated movie]]), then choose those libraries that can be trusted to [[evolution|evolve]] compatibly. | ||

+ | |||

+ | ==== Hide Incompatibilities! === | ||

+ | |||

+ | If you happen to reuse a library that cannot be trusted to keep its [[BackwardCompatibility]], then do whatever you can to not re-export its [[API]]s! This has been discussed in [[Chapter 10]], Cooperating with Other [[API]]s, but in short: If you hide such library for internal use and do not export any of its interfaces, you can use whatever version of library you want (even few years older) and nobody shall notice (unless you do re-export some of its interfaces). Moreover in many [[modular systems]] there can even be multiple versions of the same library in case they are not re-exported. |

## Revision as of 07:33, 25 August 2009

This page describes a way to convert any 3SAT problem to a solution of finding the right configuration from conflicting libraries in a system that can re-export APIs. Thus proving that the later problem is wikipedia::NP-complete.

## Contents |

## 3SAT

The problem of satisfying a logic formula remains **NP**-complete even if all expressions are written in *wikipedia::conjunctive normal form* with 3 variables per clause (3-CNF), yielding the **3SAT** problem. This means the expression has the form:

- ...

where each *x*_{ab} is a variable *v*_{i} or a negation of a variable . Each variable *v*_{i} can appear multiple times in the expression.

## Module Dependencies Problem

Let *A*,*B*,*C*,... denote various APIs.

Let *A*_{1},*A*_{1.1},*A*_{1.7},*A*_{1.11} denote compatible versions of API *A*.

Let *A*_{1},*A*_{2.0},*A*_{3.1} denote incompatible versions of API *A*.

Let *A*_{x.y} > *B*_{u.v} denote the fact that version *x.y* of API A depends on version *u.v* of API *B*.

Let denote the fact that version *x.y* of API A depends on version *u.v* of API *B* and that it re-exports *B'*s elements.

Let *Repository* *R* = (*M*,*D*) be any set of modules with their various versions and their dependencies on other modules with or without re-export.

Let C be a *Configuration* in a repository *R* = (*M*,*D*), if
, where following is satisfied:

- - each re-exported dependency is satisfied with some compatible version
- - each dependency is satisfied with some compatible version
- Let there be two chains of re-exported dependencies and then - this guarantees that each class has just one, exact meaning for each importer

#### Module Dependency Problem

Let there be a repository *R* = (*M*,*D*) and a module . Does there exist a configuration *C* in the repository *R*, such that the module , e.g. the module can be enabled?

## Conversion of 3SAT to Module Dependencies Problem

Let there be 3SAT formula with with variables *v*_{1},...,*v*_{m} as defined above.

Let's create a repository of modules *R*. For each variable *v*_{i} let's create two modules and , which are mutually incompatible and put them into repository *R*.

For each formula
let's create a module *F*^{i} that will have three compatible versions. Each of them will depend on one variable's module. In case the variable is used with negation, it will depend on version *2.0*, otherwise on version *1.0*. So for the formula

we will get:

All these modules and dependencies add into repository *R*

Now we will create a module *T*_{1.0} that depends all formulas:

- ...

and add this module as well as its dependencies into repository *R*.

**Claim**: There (a configuration) of repository *R* and there is a solution to the 3SAT formula.

## Proof

"": Let's have an evaluation of each variable to either true or false that evaluates the whole 3SAT formula to true. Then

It is clear from the definition that each *M*^{i} and *F*^{i} can be in the *C* just in one version. Now it is important to ensure that each module is present always at least in one version. This is easy for *M*^{i} as its *v*_{i} needs to be true or false, and that means one of or will be included. Can there be a *F*^{i} which is not included? Only if but that would mean the whole *3-or* would evaluate to false and as a result also the 3SAT formula would evaluate to false. This means that dependencies of *T*_{1.0} on *F*^{i} modules are satisfied. Are also dependencies of every satisfied? From all the three versions, there is just one , the one its *x*_{iq} evaluates to true. However *x*_{iq} can either be without negation, and as such depends on which is included as *v*_{j} is true. Or *x*_{iq} contains negation, and as such depends on which is included as *v*_{j} is false.

"": Let's have a *C* configuration satisfies all dependencies of *T*_{1.0}. Can we also find positive valuation of 3SAT formula?

For *i*-th *3-or* there is dependency which is satisfied. At least by one from or or . The one *F*^{i} that has the satisfied dependency reexports (which means *v*_{j} = *t**r**u**e*) or (which means *v*_{j} = *f**a**l**s**e*). Anyway each *i* *3-or* evaluates to *t**r**u**e*.

The only remaining question is whether a *C* configuration can force truth variable *v*_{j} to be true in one *3-or* and false in another. However that would mean that there is re-export via and also another one via . However those two *chain of dependencies* ending in different versions of *M*^{j} cannot be in one *C* as that breaks the last condition of configuration definition. Thus each *M*^{j} is represented only by one version and each *v*_{j} is evaluated either to true or false, but never both.

The 3SAT formula's evaluation based on the configuration *C* is consistent and satisfies the formula.

**qed**.

## Conclusion

If there is a repository of modules in various (incompatible) versions, with mutual dependencies and re-export of their APIs, then deciding whether some of them can be enabled is NP-complete problem.

As NP-complete problems are hard to solve, it is usually our best desire to avoid them in real life situations. What does that mean in case one decides to practise DistributedDevelopment (and it is inevitable that software for 21st century needs this development style)? If you want to avoid headaches with finding the right configuration of various version of the libraries that allows to execute them together, then stick with following simple rules.

#### Be Compatible!

If you develop your own libraries in backward compatible way, you can always select the most recent version of each library. That is the configuration you are looking for. It is easy to find (obviously) and also it is the most desirable, as it delivers the most modern features and bugfixes that users of such libraries want.

#### Reuse with Care!

If you happen to reuse libraries (and you should because reuse lowers Time to Market, just like it did for me when publishing my first animated movie), then choose those libraries that can be trusted to evolve compatibly.

### = Hide Incompatibilities!

If you happen to reuse a library that cannot be trusted to keep its BackwardCompatibility, then do whatever you can to not re-export its APIs! This has been discussed in Chapter 10, Cooperating with Other APIs, but in short: If you hide such library for internal use and do not export any of its interfaces, you can use whatever version of library you want (even few years older) and nobody shall notice (unless you do re-export some of its interfaces). Moreover in many modular systems there can even be multiple versions of the same library in case they are not re-exported.