Konovalov, Vadim wrote:
>  > >>In my opinion, this is perl/Tk's fault in a name clash.

>  > 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;
>  > }
>  
>  With all the respect, this code is useful and able to help to 
>  develop perl/Tk compatibility within Tcl::Tk, but have little 
>  to do with a coexistance problem, when using both modules 
>  results in segmentation fault.

Hmmm, I will disagree because if we see the coexistence as an
insurmountable bug, the above is a valid work-around.  The
question is whether it is possible to support Tcl.pm and
Perl/Tk loaded simultaneously.  If that's fundamentally not
in the cards (Stephane's option of renaming all the functions
is a bit extreme), then this at least prevents crashes, right?

Jeff



-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
Tcltk-perl mailing list
Tcltk-perl@[...].net
https://lists.sourceforge.net/lists/listinfo/tcltk-perl