Hmm Thomas,

Sounds very interesting. I've been doing a lot of work writing lexers  
for Saffron so I could be of assistance if I find the time in the  
future. But I have some questions. Are you planning to do a full  
compiler that supports embedded images, fonts, sound, etc. or just an  
Actionscript one. Also what VM are you planning to target AVM1( Flash  
8 and lower) or AVM2(Flash 9). I think a Flash 9 is needed. While  
Actionscript 3 is a great improvement it's a far cry from far more  
mature and professional languages like Objective C, C# or even Java.  
There are a lots and LOTS of things in Actionscript 3 that need to be  
added in order to make it into a mature language and I think that an  
open source AVM2 compiler would be great. This way the community  
could decided what features to add in and not some folks somewhere  
locked up in some ivory tower consortium!

Cheers,
Sam

On Sep 9, 2007, at 5:51 AM, Thomas Quester wrote:

> Mark,
>
> Thanks for all the information, the new VM seems to be cool and  
> mighty and
> good documented and easier to read.
>
>> From the compilers point of view, it creates a stricly typed one  
>> operand
> stack code with type conversion calls (if nessary) using an output  
> class,
> which may be replaced to focus differnt targets, currently  
> supported is
> assembly text output for the old VM but there have also been output  
> for a vm
> on an embedded device on which bytes are real bytes.
>
>> From what I found out until now -- based on the old vm-- there may  
>> be some
> optimizations in code by adding elements to the input language, for  
> example
> it seems that getMember for array elements is expensive because all  
> arrays
> are associative arrays (having string or numeric index). Laying out  
> "dim
> chessboard(8,8) as integer" as flat 64 elements array instead of  
> instead of
> "var chessboard:Array" would get rid of one call to getMember,  
> accessing
> elements by chessboard[x+y*8] (or x+y<<3 after optimization)  
> instead of
> twice calling getMember. If we really want want to implement the  
> minimax
> algorythm a few nanoseconds on each array access will make some  
> difference
> at the end.
> Another idea is implementing a general assembly language, something  
> like
> "var foo:Number" and later "push foo", "push myarray[foo]" and so on
> approving names from the input language and expression evaluation in
> assembly parts.
>
> Thomas
>
>
>
> ----- Original Message -----
> From: "Mark Winterhalder" <[EMAIL PROTECTED]>
> To: "Open Source Flash Mailing List" <[email protected]>
> Sent: Sunday, September 09, 2007 5:23 AM
> Subject: Re: [osflash] Anybody interest in developing a new compiler?
>
>
>>> What I do not have
>>>    _any_ expericence with flash ....    (and therefor lots of _silly
>>> questions)
>>
>> Since you mentioned you don't know much about Flash yet:
>>>> From your usage of flasm I take it that you're targeting the old  
>>>> VM,
>> so just to make sure you know, there has been a new one introduced in
>> Flashplayer 9. Adobe donated it to Mozilla, the Tamarin project [1].
>>
>> There's Adobe's AS3 compiler (which will be Open Source as part of  
>> the
>> Flex 3 SDK [2]), haXe [3] of course, and it seems like we'll be
>> getting IronRuby and IronPython soon, too [4].
>> Opcodes are supported by hxASM [5] and Swfmill (on svn [6]).
>>
>> HTH,
>> Mark
>>
>> [1] <http://en.wikipedia.org/wiki/Tamarin_(JIT)>
>> [2] <http://labs.adobe.com/technologies/flex/sdk/>
>> [3] <http://haxe.org/>
>> [4]
>> <http://weblogs.mozillazine.org/roadmap/archives/2007/07/ 
>> new_projects.html>
>> [5] <http://haxe.org/hxasm>
>> [6] <http://swfmill.org/trac/browser/trunk/src/codegen/source.xml>
>> (1483ff)
>>
>>
>>
>>
>>
>> On 9/8/07, Thomas Quester <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>> Hi list members,
>>>
>>> Is anybody interested in helping in developing a new compiler?.
>>>
>>> What I have:
>>>   A compiler accepting something between Visual Basic and Action  
>>> Script
>>> and
>>> producing source code for FLASM with original code as comments.
>>>   Some ideas for producing fast, short and probably nice obfuscated
>>> assembler code.
>>>
>>> What I want:
>>>   Easy to use language which produces either .swf or output for  
>>> swfmill
>>> and
>>> flasm accepting most VB and AS code and some elements of C like  
>>> inline
>>> functions.
>>>   Code optimizer at least for some silly optimizatoins
>>>
>>> What I do not have
>>>    _any_ expericence with flash ....    (and therefor lots of _silly
>>> questions)
>>>
>>> What I am looking for
>>>
>>>   persons answering silly questions, lots of small samples etc.
>>>
>>> Greetings
>>>
>>> Thomas Quester
>>>
>>> _______________________________________________
>>> osflash mailing list
>>> [email protected]
>>> http://osflash.org/mailman/listinfo/osflash_osflash.org
>>>
>>>
>>
>> _______________________________________________
>> osflash mailing list
>> [email protected]
>> http://osflash.org/mailman/listinfo/osflash_osflash.org
>>
>
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to