Re: Method returning non-scalar

Germain Garand wrote:
> Le Lundi 22 Novembre 2004 21:40, Ole Christensen a écrit :
> 
>>Germain Garand wrote:
>>
>>>Le Lundi 22 Novembre 2004 10:58, Ole Christensen a écrit :
>>>
>>>>Is this the way it is meant to be?
>>
>>What I wanted to say is:
>>
>>Is this intended by design?
> 
> 
> certainly not ;(
> 
> 
>>Sorry, seems you got me wrong. 
> 
> 
> No, I just attempted a bad pun :-)
> But that's indeed upseting because I had that limitation under the eyes for a 
> long long time, and just didn't realize how bad it was.

Ok, so it is me who got you wrong. I just was not sure and I did not 
want to have that dim feeling stay around.

One addition: You probably know but for those who don't: It is Ok to 
call methods returning lists (hashes too?) from within a package. So if 
we had a second sub "Test::b" in my original code snippet, that could 
properly call "a" and get the returned list.

And another but final remark: It seems PerlQt attributes are writable 
from the package itself but not from inheritors. Read access works fine 
if preceeding the attribute with an "&". So they are a kind of between 
private and protected (borrowed from C++). Haven't tried pulic read 
access. That's another item for a FAQ I guess.

Everthing above true and maybe only true for PerlQt 3.008.

Cheers,
Ole.

> 
> 
>>perfectly live with this restriction in PerlQt. Only good to know it. It
>>cost me some hours searching for the problem and turning the lists into
>>refs of them. Anyway PerlQt has saved me a lot more than this time ;-)
>>
> 
> 
> Still,  we'll work on fixing it :)
> Greetings,
> Germain