-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Add get_resource_id() function #5427
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--TEST-- | ||
get_resource_id() function | ||
--FILE-- | ||
<?php | ||
|
||
$file = fopen(__FILE__, 'r'); | ||
|
||
// get_resource_id() is equivalent to an integer cast. | ||
var_dump(get_resource_id($file) === (int) $file); | ||
|
||
// Also works with closed resources. | ||
fclose($file); | ||
var_dump(get_resource_id($file) === (int) $file); | ||
|
||
?> | ||
--EXPECT-- | ||
bool(true) | ||
bool(true) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess resource-ids will be re-used across request boundaries? if so, should be mentioned somewhere
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd agree it should be documented. Obviously, this RFC doesn't change the existing behavior, changing it here is definitely out of scope, and the same note also applies to (int)$resource.
(e.g. "currently, resource ids are unique for the lifetime of execution (e.g. an http request in a web server), but this may change, because it's limited to
2**32
on 32-bit platforms)I guess part of the issue is that it's using an associative array from integers to strings, and that zend_hash_index_del doesn't reset the last array pointer. I guess the only place where this could matter is that long-running 32-bit applications that create a lot of resources would possibly be affected by this (only able to create 4 billion ids in a lifetime for sockets/files, unless I misunderstood how this works), but for 64-bit applications, it doesn't matter.
Alternately, I guess it'd be possible to maintain a "free list" like what objects do so that resource ids can be reused.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TysonAndre It's a known issue, see https://bugs.php.net/bug.php?id=47396.