Opened 2 years ago
Closed 2 years ago
#16813 closed enhancement (fixed)
PHP5-port - Deprecate wp_clone()
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.2 |
| Component: | General | Version: | 3.1 |
| Severity: | normal | Keywords: | has-patch |
| 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)
- Milestone changed from Awaiting Review to Future Release
- Type changed from defect (bug) to enhancement
Related: #16920 - contains a patch that deprecates the wp_clone() function (only).
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.
- Resolution set to fixed
- Status changed from new to closed
- 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.
comment:8
aaroncampbell — 2 years ago
That does seem like a comment that belongs as a Trac ticket for a future release instead of in the code.

Oh so fine.