>Hmm, what does "not allow" mean? I haven't figured out how to code up >overloaded constructors, but for other methods, I was thinking we could teach >the compiler to generate >decorated function names sort of like I remember C++ >doing back in my Windows programming days.
Many moons ago in the prototype work I was doing for Spoon, I was trying the following with the compiler: function foo( value1:String ):void; function foo( value1:String, value2:int ):void; function foo( value1:Bar, value2:int ):void; would become: function fooString( value1:String ):void; function fooStringInt( value1:String, value2:int ):void; function fooBarInt( value1:Bar, value2:int ):void; Where I got stuck was also trying to regenerate a new function foo( ...args ):void; which would figure out which of the other methods to call if someone tried to invoke this in dynamic code that I could not check/change at compile time. Mike
