ID:               28016
 Comment by:       admin at php dot kz
 Reported By:      php at ter dot dk
 Status:           Assigned
 Bug Type:         Scripting Engine problem
 Operating System: *
 PHP Version:      4CVS, 5CVS (2004-04-16)
 Assigned To:      derick
 New Comment:

have same bug with crack lib


Previous Comments:
------------------------------------------------------------------------

[2004-04-16 15:11:33] [EMAIL PROTECTED]

Derick: I agree, just change gettype() too.

And imlib / other extensions using the wrong way in registering
resources should be fixed. The 'non-named' resource is meant for
something else..


------------------------------------------------------------------------

[2004-04-16 11:05:22] [EMAIL PROTECTED]

If the imlib extension gives it a proper name then it should work fine,
so I think it's also a bug there.

------------------------------------------------------------------------

[2004-04-16 08:37:21] php at ter dot dk

But will it solve the problem in my situation? After all, I do have a
resource by hand, and would be pretty sad if other functions wouldn't
recognize it as a resource.

I do agree though that making gettype not return "resource" for a
closed resource (since is_resource() already does that). I just don't
like the idea that these functions might not recognize my resource at
all.

- Peter Brodersen

------------------------------------------------------------------------

[2004-04-16 03:15:17] [EMAIL PROTECTED]

No, the fix was correct. Close() in this case destroyed the resource
data in the variable, so it's no longer a resource anymore. I think the
correct thing to do here is to make gettype() not show "resource"
either.

------------------------------------------------------------------------

[2004-04-15 22:35:54] [EMAIL PROTECTED]

Derick, IMO, the fix for bug #27822 was incorrect. 
Resource is still a resource even if it's closed..
Or you need to unset the variable with any 'close'.. :)


------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/28016

-- 
Edit this bug report at http://bugs.php.net/?id=28016&edit=1

Reply via email to