Hi,
is not practical for me to add an undefined test because the
concatenation is done inside the mason library.
I would like to know from where the undefined value comes but, as the
component works as expected, more important to me now is to remove those
annoying warnings.
Cheers,
Javie
El sáb, 03-05-2008 a las 10:34 +0900, Raymond Wan escribió:
> Hi Javier,
>
> Javier Amor García wrote:
> > I have looked to the Subcomponent.pm code and the exact line is this:
> > $self->{path} = $self->owner->path . ":" . $self->name;
> >
> > Debuging a little I have seen that the undefined value comes from
> > $self->owner->path; ($self->name have the correct value)
> >
> >
> > Somebody can help me to get rid of this warnings?
> >
>
>
> I don't understand...you seemed more concerned about getting rid of the
> warning and less concerned about why $self->owner->path is always
> undefined :-) . You're essentially concatenating to an undefined
> value. Why don't you add a test to see if it is defined and concatenate
> only of it is?
>
> Ray
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
