Re: Another clarification of the static library packaging guidelines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 06, 2010 at 11:23:07AM +0200, Michael Schwendt wrote:
> *confused*  Then there is no difference compared with libs compiled
> from C (or C++ or other programming languages, which are compiled into
> native code). So, why do you mention C?

Well C/C++ code suffers from several classes of error which don't
affect other languages, and this is what makes static linking
particularly undesirable for C libraries.  The other reason for
avoiding static linking -- avoiding duplication of code -- happens
anyway in C libraries (think: headers/inlining), and even more so in
the OCaml compiler which does cross-module inlining when possible.

Anyway, see my other reply for more details about what OCaml is doing.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging


[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux