Stephane Chatty wrote:
> >In my opinion, this is perl/Tk's fault in a name clash.
>  
>  
>  Same opinion. But I have the vague feeling that the name clash is part
>  of the trick in perl-Tk: have Tk run over a fake Tcl library that relies
>  on Perl internals.

Yes, this is almost certainly the problem.  I actually put
some code in to handle this, but I see that I made it only
trigger in debug mode (in Tk.pm):

if (DEBUG()) {
     # The gestapo throws warnings whenever Perl/Tk modules are 
requested.
     # It also hijacks such requests and returns an empty module in its 

     # place. 

     unshift @INC, \&tk_gestapo;
}

You can see the def'n later in Tk.pm, but it basically hijacks
'use Tk' and related requests.  Since there is a naming issue,
we should probably reinstate this as a default, and change
from warning to error if we aren't fully hijacking and
replacing the content (which actually, I think we can do).

-- 
   Jeff Hobbs, The Tk Guy
   http://www.ActiveState.com/, a division of Sophos


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Tcltk-perl mailing list
Tcltk-perl@[...].net
https://lists.sourceforge.net/lists/listinfo/tcltk-perl