Re: Loom viability

On Fri, 19 Dec 2003 04:28 am, Terry Laurenzo wrote:
> I guess it doesn't need any extensions, but the state that this feature
> was in for the last 4.1 Phoenix snapshot I got (admittedly a long time
> ago) was pretty shaky.  It seemed as though practically the entire
> Phoenix kernel assumed one-to-one relationships between components and
> this feature was something of a square peg in a round hole (but a much
> needed square peg!).  I remember submitting some fixes to it back in
> the day that made it useable... I'll take a look at source for this, as
> I was pretty familiar with it and aware of some of the areas where it
> needed improvement.  

kool.

> If I recall, the particular limitation that it
> suffered from was that you had to declare at least one instance in an
> array or map dependency... there was no way to get back in empty array
> or map from the service(...) method.

Add an issue to the Loom Issue tracker and we will hopefully get around to 
"fixing" this. Or alternatively you could assign the issue to yourself and we 
would gladly apply any patches you send ;)

-- 
Cheers,

Peter Donald
"Some cause happiness wherever they go; 
others, whenever they go." 
          - Oscar Wilde (1854-1900)