New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tk::Event::IO::fileevent() corrupts inheritted IO::Sockets #1962
Comments
From gavin.brock@nssmb.comCreated by zaragoza@usa.netThe following code fails: package Foo; sub new { $$obj->{Foo_prop1} = "value1"; # OK, foo's property ## The above line badly ties the object, return $obj; package main; Error: I can work arroun this, by duping my $obj as a IO::Handle, but it's ugly. Why Cheers, Gavin Perl Info
|
From [Unknown Contact. See original ticket]Gavin Brock <zaragoza@usa.net> writes:
It does not "badly tie" it it ties it with TIEHANDLE.
You could also work round it by defining : sub Tk::Event::IO::FETCH
So that:
So what should I do ? - popup a dialogue ->messageBox(-message => "May I tie $obj", -type => 'YesNo') You have (via the fileevent call) "given" the object to Tk. |
From [Unknown Contact. See original ticket]Nick Ing-Simmons writes:
Which is not expected, thus bad.
If so, this should have been done by Tk itself. But I doubt it. $tk->fileevent($obj, 'readable', sub {warn "FooBar"}); $obj is probably a glob ref, right? $$obj->{Foo_prop1} = "value1"; $obj is a hash ref ref, right? I'm confused. Unles a glob can work as a hash ref in the above syntax, and you tie Ilya |
From [Unknown Contact. See original ticket]Ilya Zakharevich <ilya@math.ohio-state.edu> writes:
fileevent is passed a filehandle - it happens to implement its
Why - Tk was expecting to be passed a file handle (globref) - it was not
Yes.
I assumed that syntax is messing with the hash part of the glob via |
From [Unknown Contact. See original ticket]On Sat, May 13, 2000 at 10:41:15AM +0100, Nick Ing-Simmons wrote:
... and *this* is a bug. If Tk meeds messing with the FH, it should be messing with IO part of the Ilya |
From [Unknown Contact. See original ticket]Ilya Zakharevich <ilya@math.ohio-state.edu> writes:
Ok. But as far as I am aware you have to pass a glob to tie to achieve What I have at present is: sub fileevent I will gladly change that to any incantation which will effect a tie |
From [Unknown Contact. See original ticket]On Sat, May 13, 2000 at 02:59:37PM +0100, Nick Ing-Simmons wrote:
Then *this* is a bug. ;-) Or if it is not, the fact that
No warning on re-tie()ing? [Not that it will help in the discussed case...] Ilya |
From [Unknown Contact. See original ticket]Ilya Zakharevich (lists.p5p):
I seriously hate to say this, but in the past two days you have |
From [Unknown Contact. See original ticket]Simon Cozens writes:
And your point is "So shut up"? Sorry, but you need to have more And BTW, this is going to continue. I'm not interested much in perl Hope this helps, |
From [Unknown Contact. See original ticket]Nick, Ilya, I sent a reply on this thread a while back, but it seems to have However, I then tested under 5.6.0, when I tried to access the hash key in (in cleanup) Can't call method "FETCH" on an undefined value at test.pl Below is the perl-bug output for my 5.6 build. Cheers, Gavin Perl Info
|
From [Unknown Contact. See original ticket]On Sun, May 14, 2000 at 11:12:56PM +0900, Gavin Brock wrote:
Here is the problem: perl -MDevel::Peek -wle "sub a::TIEHANDLE {bless []} tie *x,'a'; Dump \*x" There is no reason why this tie should have set SMG and RMG flags. Ilya |
From @chornyOn perl 5.14.0, output is "FLAGS = (MULTI,IN_PAD)" and example from the On Sun May 14 02:48:14 2000, RT_System wrote:
-- |
@iabyn - Status changed from 'open' to 'resolved' |
From gavin@brock-family.orgThanks Alexandr, never expect to see this old one show up again!! Have |
Migrated from rt.perl.org#3235 (status was 'resolved')
Searchable as RT3235$
The text was updated successfully, but these errors were encountered: