[mtasc] -xml switch
Benjamin C. Allfree
benles at bldigital.com
Sun Sep 18 23:57:09 CEST 2005
It might be nice to have an -xml switch that controlled compiler output
format. I think this would help with IDE projects that try to capture the
Something like this:
mtasc.exe -xml -swf test.swf -header 800:600:30 test.as
test.as:20: lines 20-358 : type error class not found : NoClass
test.as:1: characters 3-4 : parse error Unexpected x
<message type="Error" filename="test.as" line="20" lineStart="20"
lineEnd="358"> type error class not found : NoClass</message>
<message type="Error" filename="test.as" lineStart="1" characterStart="3"
characterEnd="4">parse error Unexpected x</message>
> -----Original Message-----
> From: mtasc-bounces at lists.motion-twin.com [mailto:mtasc-
> bounces at lists.motion-twin.com] On Behalf Of Nicolas Cannasse
> Sent: Sunday, September 18, 2005 1:59 AM
> To: MotionTwin ActionScript2 Compiler List
> Subject: Re: [mtasc] Strongly Typed Arrays in MTASC
> > I understand that this syntax can easily be "mixed" with
> > normal comments (let's say the type was changed 'temporarily',
> > leaving the previous type commented out next to it).
> I choose the syntax to be the most easy possible. Please notice that it's
> only used when present on the left side of an "Array" type, so for example
> the following :
> var a : /* some comments */ Number;
> Will compile just fine. In fact the only problem is that if you do :
> var a : /* some comment */ Array;
> Which I think is pretty unlikely to happen.
> I guess that /*Number*/ Array is already informative enough and doesn't
> need additional syntax rules :
> - for MTASC users it says this is a strongly typed Array
> - for MMC users it give some comment on the content of the Array
> Also I think it's great to be able to have such a feature without the
> of breaking compatibility with MMC.
> MTASC : no more coffee break while compiling
More information about the mtasc