RE: inheritance issue...

By answering the question? 

Is there a problem with multiple inheritance in mtasc? There
seem to be
messages in the archives of this list but nothing that seems
to suggest
why this particular case is occurring....

Thanks for you reply, though, really helpful

t

-----Original Message-----
From: mtasc-bounceslists.motion-twin.com
[mailto:mtasc-bounceslists.motion-twin.com] On Behalf Of Eric
Priou
Sent: 22 February 2007 14:19
To: MotionTwin ActionScript2 Compiler List
Subject: Re: [mtasc] inheritance issue...


> My Team Leader feels it's about multiple inheritance...
I don't - can

> anyone shed any light on this?
How could we ?
----
Eric Priou
aka  erixtekila
Articles : http://www.v-i-a.net/
inprogress
Oregano : http://www.v-
i-a.net/inprogress/oregano



-- 
MTASC : no more coffee break while compiling

--
MTASC : no more coffee break while compiling

As nearly as I can tell and from your own tests, multiple
levels of 
inheritance are not a problem.

Ron

Trevor Burton wrote:
> By answering the question? 
>
> Is there a problem with multiple inheritance in mtasc?
There seem to be
> messages in the archives of this list but nothing that
seems to suggest
> why this particular case is occurring....
>
> Thanks for you reply, though, really helpful
>
> t
>
> -----Original Message-----
> From: mtasc-bounceslists.motion-twin.com
> [mailto:mtasc-bounceslists.motion-twin.com] On
Behalf Of Eric Priou
> Sent: 22 February 2007 14:19
> To: MotionTwin ActionScript2 Compiler List
> Subject: Re: [mtasc] inheritance issue...
>
>
>   
>> My Team Leader feels it's about multiple
inheritance... I don't - can
>>     
>
>   
>> anyone shed any light on this?
>>     
> How could we ?
> ----
> Eric Priou
> aka  erixtekila
> Articles : http://www.v-i-a.net/
inprogress
> Oregano : http://www.v-
i-a.net/inprogress/oregano
>
>
>
>   

-- 
MTASC : no more coffee break while compiling

I am not sure that the Flash player can tell the difference
between your 
test runs and your production runs.
If inheritance works in "Test" it works in
"Production"

Ron


Trevor Burton wrote:
> By answering the question? 
>
> Is there a problem with multiple inheritance in mtasc?
There seem to be
> messages in the archives of this list but nothing that
seems to suggest
> why this particular case is occurring....
>
> Thanks for you reply, though, really helpful
>
> t
>
> -----Original Message-----
> From: mtasc-bounceslists.motion-twin.com
> [mailto:mtasc-bounceslists.motion-twin.com] On
Behalf Of Eric Priou
> Sent: 22 February 2007 14:19
> To: MotionTwin ActionScript2 Compiler List
> Subject: Re: [mtasc] inheritance issue...
>
>
>   
>> My Team Leader feels it's about multiple
inheritance... I don't - can
>>     
>
>   
>> anyone shed any light on this?
>>     
> How could we ?
> ----
> Eric Priou
> aka  erixtekila
> Articles : http://www.v-i-a.net/
inprogress
> Oregano : http://www.v-
i-a.net/inprogress/oregano
>
>
>
>   

-- 
MTASC : no more coffee break while compiling

> By answering the question?
Obviously.
But I just had the feeling that you just gave too few
details.
>
> Is there a problem with multiple inheritance in mtasc?
There seem  
> to be
> messages in the archives of this list but nothing that
seems to  
> suggest
> why this particular case is occurring....

BTW, I had the sale kind of issue once.
But when I've thought of it after, I can't see any trouble
in multi- 
level inheritance chain.

As anyone knows, the inheritance is built backward from the
__proto__  
property.
As any other pointer in flash, the variables are passed by
reference  
for complex data (not primitive)
Then we should conclude that there couldn't get any problem
with long  
inheritance chain because it's the same principe.

If the inheritance is broken, it do mean that the
myObject.__proto__  
is not set correctly or unset at a time.
Who still continue to use the prototype property inside
class's  
methods ?
Who use mixins like EventDispatcher.initialize ?
Maybe some part of your code do use those practices.

But definitively I think that inheritance is kept.

But maybe could you use composition to fix your very problem
?


Sorry to ping you back with my question.
HTH
----
Eric Priou
aka  erixtekila
Articles : http://www.v-i-a.net/
inprogress
Oregano : http://www.v-
i-a.net/inprogress/oregano



-- 
MTASC : no more coffee break while compiling

I'm not aware of a general issue with inheritance. Maybe you
can
reduce your problem and show us some code?

Cheers
Ralf.

On 2/22/07, Eric Priou <erixtekilagmail.com> wrote:
> > By answering the question?
> Obviously.
> But I just had the feeling that you just gave too few
details.
> >
> > Is there a problem with multiple inheritance in
mtasc? There seem
> > to be
> > messages in the archives of this list but nothing
that seems to
> > suggest
> > why this particular case is occurring....
>
> BTW, I had the sale kind of issue once.
> But when I've thought of it after, I can't see any
trouble in multi-
> level inheritance chain.
>
> As anyone knows, the inheritance is built backward from
the __proto__
> property.
> As any other pointer in flash, the variables are passed
by reference
> for complex data (not primitive)
> Then we should conclude that there couldn't get any
problem with long
> inheritance chain because it's the same principe.
>
> If the inheritance is broken, it do mean that the
myObject.__proto__
> is not set correctly or unset at a time.
> Who still continue to use the prototype property inside
class's
> methods ?
> Who use mixins like EventDispatcher.initialize ?
> Maybe some part of your code do use those practices.
>
> But definitively I think that inheritance is kept.
>
> But maybe could you use composition to fix your very
problem ?
>
>
> Sorry to ping you back with my question.
> HTH
> ----
> Eric Priou
> aka  erixtekila
> Articles : http://www.v-i-a.net/
inprogress
> Oregano : http://www.v-
i-a.net/inprogress/oregano
>
>
>
> --
> MTASC : no more coffee break while compiling
>


-- 
Ralf Bokelberg <ralf.bokelberggmail.com>
Flex & Flash Consultant based in Cologne/Germany
Phone +49 (0) 221 530 15 35

-- 
MTASC : no more coffee break while compiling