Itcl - the [incr Tcl] extension

Ticket Change Details

Artifact ID: 4143d0130d782d78035fe69f0efd69e2090d2dcf6b61638915b375a223b72b48
Ticket: 15f7db53b9f36d978ce732685ac868ee06fbb216
Different behavior for Itcl 4 and Itcl 3
User & Date: dgp 2018-03-20 13:43:08

  1. Change icomment to:

    It appears that both Itcl 3 and Itcl 4 have this command access to a method in place. In Itcl 4, though, every Itcl object is a TclOO object and every Itcl method is a TclOO method, so when you try to invoke a TclOO method (even through a command backdoor access) on a TclOO object that lacks that method, the access restrictions of TclOO catch that and report the error.

    I don't have a strong sense whether this is stopping something that was never a good idea to begin with, or whether it is exposing that TclOO and Itcl have even more deeply fundamental disagreements about their very models of operation than was ever appreciated, and that in a deep sense the Itcl 4 project of building Itcl on top of a TclOO foundation is just unworkable.

  2. Change login to "dgp"
  3. Change mimetype to "text/x-fossil-plain"