Opened 14 years ago
Closed 14 years ago
#16813 closed enhancement (fixed)
PHP5-port - Deprecate wp_clone()
Reported by: | hakre | Owned by: | nacin |
---|---|---|---|
Milestone: | 3.2 | Priority: | normal |
Severity: | normal | Version: | 3.1 |
Component: | General | Keywords: | has-patch |
Focuses: | Cc: |
Description
wp_clone() is not needed any longer. php natives can do better and php 4 does not needs to be supported any longer.
let's just deprecate it (hey, that could have been done already for 3.1).
Next to deprecation, the version check is obviously luxury (for trunk).
See Object Cloning
Reference: #13480
Attachments (1)
Change History (10)
#1
@
14 years ago
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
#2
@
14 years ago
Related: #16920 - contains a patch that deprecates the wp_clone() function (only).
#5
@
14 years ago
The APC and memcached object cache drop-ins do not use wp_clone() so moving it from load.php to deprecated.php should be safe.
#7
@
14 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
FIXME the next two lines of code are not necessary and should be removed.
Why?
Either it should be deemed as such (by a committer) or such comments should be removed until there's a decision made.
Otherwise it is confusing for people who see it.
Oh so fine.