Re: [TCLCORE] itcl/itk conversion

[Griffin, B. <bri...@me...>]

Thanks Don.  So it's still a WIP.  I'll keep plowing through this to see what I can figure out.  I'm throwing over 500k lines of tcl+tk+itcl+itk code at this all at once.  I'm running into Tk issues too, but these are a bit easier to figure out.

This may take awhile...

-Brian

From: Donald Porter <d.g...@co...<mailto:d.g...@co...>>
Date: Tuesday, July 28, 2015 at 10:25 AM
To: Brian Griffin <bri...@me...<mailto:bri...@me...>>
Cc: Tcl Core List <tcl...@li...<mailto:tcl...@li...>>
Subject: Re: [TCLCORE] itcl/itk conversion


On Jul 27, 2015, at 7:05 PM, Griffin, Brian <bri...@me...<mailto:bri...@me...>> wrote:

Is there a list of known porting issues when moving from itcl/itk 3.4 to 4.0.3?

Best thing I can offer are the two places where bug report tickets are collected.

http://sourceforge.net/p/incrtcl/bugs/

http://core.tcl.tk/itcl/rptview?rn=1

Continued progress on Itcl 4 is driven entirely by bug reports.  Any way that
Itcl 4 results depart from Itcl 3 results is at least presumptively a bug.  Short
demos (in test suite form, if possible) are the best bet to get the issue worked on.

Don’t imagine the differences are intentional or have some purpose.  They aren’t.
They’re botches that need to be noticed and flagged to get fixed.

For the most part, Itcl 4 is only going to get as good as its users demand it to be.
Developers can only know what features are wrong and which are more and less
important to get right from user demand.

The [itcl::ensemble] parser bug report was done exactly right.  Need more of that
from people who are or wish to be Itcl 4 users.

Continued tracking and testing of trunk and various branches trying out bug fixes
are helpful as well.

 I seem to be running into a number of fundamental problems that seem odd to me, like "common" not working right, and issues with options I'm still trying to understand.

DGP