Comments on: FAME Chronicles #1: Long Classpaths & Local Var Declarations

By: rob

rob — Wed, 08 Jun 2005 19:00:02 +0000

re the inner variables, and not retyping them, guess thats ok – can understand its not really good programming -as per ‘Local variables scoping’ on the mtasc.org website)

what i’ve found a pain is nested functions,which seem a different issue

from the mtasc.org website
>
that certainly stops a lot of code compiling on a current project I tried to use MTASC on – and a pain reworking the code to get rid of nested function which work ok on MM IDE (and are used in say Moock’s book)

I sort of understand the difficulty the compiler has – but surely if the number of { does not equal the number of closing } it could stop proceedings then
MM IDE can generate 71 consequent errors when you forget a paranthesis – but no-one has suggested nested functions are intrinsically bad

seems a problem to me

By: JesterXL

JesterXL — Fri, 13 May 2005 21:12:11 +0000

No, haven’t tried that, but will now that you brought up the idea!!!

By: r0main

r0main — Fri, 13 May 2005 11:29:08 +0000

Jester,
did you manage to have FAME (MTASC part) compiling AS files with Flex core classes ?

By: Andre Fuller

Andre Fuller — Tue, 10 May 2005 22:29:26 +0000

I experienced the exact same thing!
At work, I got sick of the MM compiler lunch breaks, so i got a ‘FAME’ setup going, and now I don’t even have time sip my coffee. About the local vars, I initially thought it was complete hogwash myself, until i asked a uber-programmer/coworker about it and he corrected me.

Dude, it’s like deja vu…

By: I am the walrus

I am the walrus — Sat, 30 Apr 2005 21:06:15 +0000

I compiled my Final Fantasy 3 flash emulator today and voila! It compile in .3 nanoseconds with only 2000 warnings.