RE: [Flashcoders] Weird OOP ability... Need a description of why, or at least some documentation

2006-06-02 Thread jim
Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Shefman Sent: 01 June 2006 18:08 To: flashcoders@chattyfig.figleaf.com Subject: [Flashcoders] Weird OOP ability... Need a description of why,or at least some documentation I ran across this really bizarre

RE: [Flashcoders] Weird OOP ability... Need a description of why, or at least some documentation

2006-06-02 Thread jim
PROTECTED] On Behalf Of Drew Shefman Sent: 01 June 2006 18:08 To: flashcoders@chattyfig.figleaf.com Subject: [Flashcoders] Weird OOP ability... Need a description of why,or at least some documentation I ran across this really bizarre method access while reviewing someone else's work.

Re: [Flashcoders] Weird OOP ability... Need a description of why, or at least some documentation

2006-06-01 Thread ryanm
MyTestClass(myInst).runTest(); What's weird? You're just casting myInst as a MyTestClass, which contains the function runTest in its prototype. ryanm ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archiv

Re: [Flashcoders] Weird OOP ability... Need a description of why, or at least some documentation

2006-06-01 Thread Ian Thomas
Hi Drew, That's just type casting. See my email of a few days ago. It's actually redundant in the example you provided, because the compiler already knows that it's a MyTestClass object. You could replace it with: var myInst:MyTestClass = new MyTestClass(); myInst.runTest(); If, however, for

[Flashcoders] Weird OOP ability... Need a description of why, or at least some documentation

2006-06-01 Thread Drew Shefman
I ran across this really bizarre method access while reviewing someone else's work. I would like to look up some documentation for this syntax (it doesn't have to be AS, it could be some other OOP language - if this is a standard option that I haven't seen before)... or at least get a description