4 replies to this topic

[infogulch]

This is because objects' methods are references to functions and can be manipulated dynamically, making error detection nearly impossible at load time.

E.g. modify your code:

#Warn
t := new test
t.func1(1)

t.func2 := t.func1
t.func2(2) ;this calls correctly

t.func1 := ""
t.func1(3) ;this doesn't get called at all

class test {
   func1(x) {
      msgbox %x%
   }
}

Shows "1" then "2" but not "3"

Also don't forget about the __call meta function, which would complicate error detection further.

iirc there has been talk about run-time errors when calling nonexistent methods (possibly including exceptions), but I don't remember the outcome of the conversation.

[jethrow]

Also don't forget about the __call meta function ...

Plus, I would argue that objects should build their own error handling:

#Warn
t := new test
t.func1()
t.func2() ; user defined runtime error



class Warn {
   __Call(p) {
      MsgBox, 262420, , % "Call to NonExistent Method`n`n  Class:`t" this.__Class 
                     .    "`n  Func:`t" p "`n  Line:`t" Exception("",-1).line
                     .    "`n`nContinue Script?"
      IfMsgBox, No
         ExitApp
   }
}

class test extends Warn {
   func1() {
      msgbox bla
   }
}

func1() {
   msgbox bli
}

EDIT - corrected MsgBox logic - thanks nimda.

[nimda]

That's evil :twisted:

Continue Script?
> Yes
> > Script exits