Dale Graham wrote:
Actually, if you have instantiated a TCF as a "request" within the TAF and then call a method from the same TCF, it will break if called as "method$this" - needs to be called as "request$this".
I have tafs and tcfs that would disagree with this statement.
And if instantiated in any other scope, the called internal method needs to match scope of instantiation. At least that's been my empirical experience.
when using "this" as the object name, the scope should be irrelevent. the "this" keyword implies that you want to call the method of the exact same instance of the method that is currently running. Method makes the most sense to me, because your are currently executing a method, but Instance$this would probably make more sense.
However, what I've documented in my previous email is how the two versions differ, and the Witango one definitly has "pain in the butt" potential, because dragging a method to a called within a tcf method by default will not work unless you explicitly fill in the name as this.
This (no pun intended) is a step backwards.
/John
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
