Re: ciruclar dependencies

Tor Lillqvist <tml -AT- iki.fi>
Fri, 25 May 2012 18:49:35 +0300

i believe cyclical dependencies indicate bad architecture.  if 2 modules
depend on each other, then either they should be changed not to depend
on each other, or merged into one module.


Hear, hear.

Do you include run-time dependency in that? Like the couple of places
where dynamic linking is used, to enable code in library A that
depends on library B at compile-time to be used from library B at
run-time. (I.e. B loads A and looks up one or a few functions from it
dynamically.)

--tml

Context

Re: feature/gbuild_merge needs testing (continued)
- Re: ciruclar dependencies (was: feature/gbuild_merge needs testing) · Stephan Bergmann
  - Re: ciruclar dependencies · Michael Stahl
    - Re: ciruclar dependencies · Tor Lillqvist
      - Re: ciruclar dependencies · Michael Stahl
        
        Re: ciruclar dependencies · Tor Lillqvist
        
        Re: ciruclar dependencies · Michael Stahl
        
        Re: ciruclar dependencies · Stephan Bergmann
        Re: ciruclar dependencies · Tor Lillqvist
    - Re: ciruclar dependencies · David Tardon
- Re: feature/gbuild_merge needs testing · Norbert Thiebaud
- Re: feature/gbuild_merge needs testing · Michael Meeks
  - Re: feature/gbuild_merge needs testing · David Tardon
- Re: feature/gbuild_merge needs testing · Norbert Thiebaud

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.