Dependencies of Magma 1.0r43

Miguel Enrique Cobá Martinez miguel.coba at gmail.com
Wed Jan 13 16:28:17 UTC 2010


El mié, 13-01-2010 a las 09:54 -0600, Chris Muller escribió:
> > One thing, neither Dependency Browser nor Lukas Dependency Analyzer show
> > a package that depends on Ma special collections tester.
> > In the graph this is shown as none arrow pointing to the node Ma special
> > collections tester.
> >
> > Is this intentional?
> 
> Yep.  As the name suggests, Ma special collections tester tests the
> special collections employed by Magma; most notably the critical
> MaHashIndex.

But should be loaded when loading Magma tester right?

> 
> > Or should I make Magma tester depend on Ma special collections tester
> > even though no class of this last one is used by Magma tester?
> 
> Why create an artificial dependency?

Yes, maybe dependency isn't the right word, because it doesn't use a
specific class of Ma special collections tester. I really mean that when
loading Magma Tester, Ma special collections tester is required to be
load. That is how is specified in Metacello. In fact Metacello doesn't
know if when specifying that package A requires package B that means
that a class in package A uses/references/inherits/whatever a class in
package B. Is just a way to declare that before loading package A it
should load package B.

> 
> > By the moment I will force the dependency of Magma tester on Ma special
> > collections tester in order to load it when loading Magma tester. Later
> > we can change this if neccessary.
> 
> Ah, a tool limitation, that's why..     :(

Not so, more exactly a bad explanation from me!

> 
>  - Chris

Thanks

-- 
Miguel Cobá
http://miguel.leugim.com.mx



More information about the Magma mailing list