Front page | perl.perl5.porters |
Postings from April 2000
> Okay - you mentioned Tk twice now. > What exactly is your gripe about Tk and perl5.6.0 ? No gripes, Nick. Your work is excellent and I applaud you, period. You're one of the most active and effective members in this forum and have done tremendous work for the _entire_ perl community, Win32 included. (Side note, you said a while back that you were thinking of making a MinGWin32 (GCC-Win) makefile for perl. Did that come about? If not I'll grab that task if you're willing to give it - I'd prefer that CM for one make its own Perl and not depend on a $1500 compiler, and that people, given a short tutorial, not have to depend on AS's handouts.) > The only issue that I am aware of with Tk and perl5.6.0 is that > some long deprecated coding practices (e.g. not declaring the > widgets you use) lead to peculiar error messages due to the ->isa bug. > Tk800.020 fixes that. Another update? I can't keep up. ;-)) Actually what I personally am talking about is the nv vs PL_nv set of bugs. I'm afraid I don't know enough of perlguts to know what's going on there. It seems to be the same problem present in the other modules that failed on me. Frankly, I'm not aware of any other bugs in Tk->5.6. I don't know the bugs that the others here are talking about. I haven't gotten that far in my testing. I wasn't expecting 5.6 to be released so soon after a first beta, so it caught me off guard too. > >I wouldn't say lazy, really, just overworked, tired and with more joy > >hacking and coding than maintaining; > >especially maintaining something when > >the rug is pulled out from under you. > > No rug was pulled from Tk - Tk is excessively familiar with perl's guts > and despite that extemely minimal changes were required. Given an adequate beta period, would these changes/fixes have been made before 5.6's release? > >I'm wondering whether the term > >"backwards compatibility" has escaped us. > > It is my watchword. I've noticed. Kudos.Thread Previous | Thread Next