On 2007-11-26, at 11:05 EST, Donald Anderson wrote:
Tucker,
I'm going to implement new keywords now. Here's what I'm presuming
we're doing in the short term, needed to support devildog:
final on class, method -- pass through for SWF9 only,
else remove and warn?
const instead of var -- pass through for SWF9 only, else
change to var and warn?
dynamic on class -- pass through for SWF9 only, else remove
and warn?
override on method -- pass through for SWF9 only, else remove
and warn?
Should I do these in trunk (effectively ignoring them for current
targets),
so we can start using them right away?
It could help us keep a more integrated code base for lfc.
If so, do we want to warn on either first use, every use, or never?
Warning level could be an option too. Any other keywords?
public, private?
As long as you are in the parser, it makes sense to me to handle all
these modifiers at once (however much I hate public/private -- which I
just think are at the wrong modularity). There is code in the class
runtime to support validating final/override, but let's not worry
about that now -- focus on swf9. For other runtimes, just drop them.
I suppose create a task to eventually do something useful with them in
other runtimes.
Hm. I wonder just how much of Javascript 2 Firefox already supports?
