Skip Menu |

This queue is for tickets about the Tk CPAN distribution.

Report information
The Basics
Id: 24719
Status: rejected
Priority: 0/
Queue: Tk

People
Owner: Nobody in particular
Requestors: BrigJ [...] IntoText.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: perl Tk bug--matter of documentation for After.pm?
Date: Thu, 1 Feb 2007 07:54:58 -0800 (PST)
To: bug-Tk [...] rt.cpan.org
From: Brig Johnson <intotext [...] yahoo.com>
Hi Nick (?), I found the Tk::after module recently and liked what it did for me. Since it was "working", I didn't notice messages piling up in my error log saying things like: #Subroutine _cancelAll redefined at # C:/Perl/site/lib/Tk/after.pm line 11, <DATA> line 183. #Subroutine Tk::After::Cancelled::once redefined at # C:/Perl/site/lib/Tk/after.pm line 22, <DATA> line 183. It appears that because I am on Windows, the "case" of how I invoke "after" matters, and this bug report is primarily one about documentation. (I think.) The errors appeared when I did: require Tk::after; which seemed to be specified by the NAME section of the documentation, i.e. Tk::after - Execute a command after a time delay yet a tour through PerlMonks found node http://perlmonks.org/index.pl?node_id=302959 "Windows pitfall: Subroutine redefined with use Modul" which pointed to "case" on a Windows platform as a problem. (Another PerlMonks post had me doing a "no warnings 'redefine';" which at least silenced the error messages but left me uncomfortable.) Doing: require Tk::After; made the error messages cease. I'm not sure of the implications of using 'After' or 'after', but I would think I'd prefer the "automatic cancel" behavior. Thanks, Brig Johnson Tampa, FL (813) 968-2972
On Thu Feb 01 10:55:48 2007, BrigJ@IntoText.com wrote: Show quoted text
> Hi Nick (?),
Hello Brig, Nick passed away some months ago. [...] Show quoted text
> Doing: > require Tk::After; > made the error messages cease. I'm not sure of the implications of > using 'After' or 'after', but I would think I'd prefer the > "automatic cancel" behavior. >
You have to be careful with capitalization of perl modules. When you use case-insensitive filesystems (like under Windows), then "use Tk::after" and "use Tk::After" will both work, but load the *same* file twice, hence the "redefine" warnings. Better to stick to the official name, which would be Tk::After. Regards, Slaven
Subject: Re: [rt.cpan.org #24719] perl Tk bug--matter of documentation for After.pm?
Date: Sun, 4 Mar 2007 17:20:33 -0800 (PST)
To: bug-Tk [...] rt.cpan.org
From: Brig Johnson <intotext [...] yahoo.com>
Hello Slaven, Thank you for your personal reply and clarification for my question. Your message about Nick kind of shocked/numbed me because I think of Tk as a huge rollicking toolset driven onwards by an energetic rollicking guy. I am sorry to hear the news and hope his family and friends are okay. Thank you again for looking after the project. I may have some questions for you in the future about Tk matters if you do consulting on the subject. Best, Brig Johnson IntoText Corp. Tampa, FL +1 813-968-2972 Slaven_Rezic via RT <bug-Tk@rt.cpan.org> wrote: On Thu Feb 01 10:55:48 2007, BrigJ@IntoText.com wrote: Show quoted text
> Hi Nick (?),
Hello Brig, Nick passed away some months ago. [...] Show quoted text
> Doing: > require Tk::After; > made the error messages cease. I'm not sure of the implications of > using 'After' or 'after', but I would think I'd prefer the > "automatic cancel" behavior. >
You have to be careful with capitalization of perl modules. When you use case-insensitive filesystems (like under Windows), then "use Tk::after" and "use Tk::After" will both work, but load the *same* file twice, hence the "redefine" warnings. Better to stick to the official name, which would be Tk::After. Regards, Slaven