[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-commit] /srv/bzr/gnash/trunk r11006: create two arrays of ini
From: |
Rob Savoye |
Subject: |
Re: [Gnash-commit] /srv/bzr/gnash/trunk r11006: create two arrays of init functions, one for as2, and one for as3. |
Date: |
Fri, 05 Jun 2009 16:14:11 -0600 |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090409) |
strk wrote:
> The rationale for keeping the AS class headers clean was two fold:
> 1) we reduce build times as classes are implemented
Which is a bogus reason we don't need to worry about.
> 2) we avoid the temptation to use classed directly from internal
> code, which usually bring to incompatibilities (see how the
> array class ended up being incompatible with the pp which
> expects it to be accessed like normal objects)
Which seems like a silly way of forcing the programmer to do the right
thing, but I can understand the "safety" aspect. I don't really care
where classes are defined, it's just my long-time habit to define them
in headers, so that was what I did when I generated the new AS3 classes.
The real issue is whether to use the older *_class_init() or
Class::init() style of initializing.
- rob -