summaryrefslogtreecommitdiff
path: root/Zend/ZEND_CHANGES
diff options
context:
space:
mode:
authorSebastian Bergmann <sebastian@php.net>2001-12-16 20:28:18 +0000
committerSebastian Bergmann <sebastian@php.net>2001-12-16 20:28:18 +0000
commitcc01431199e322beedbfb0dd08e84277f84c3b29 (patch)
treea2d719c7e1783a2d8570fd9fb8986a39a64af308 /Zend/ZEND_CHANGES
parent7920d4fc7e17b686e6d7fb0ba3b04e6940152047 (diff)
downloadphp-git-cc01431199e322beedbfb0dd08e84277f84c3b29.tar.gz
I'm too trigger-happy.
Diffstat (limited to 'Zend/ZEND_CHANGES')
-rw-r--r--Zend/ZEND_CHANGES4
1 files changed, 2 insertions, 2 deletions
diff --git a/Zend/ZEND_CHANGES b/Zend/ZEND_CHANGES
index c9605337c6..57b02ea677 100644
--- a/Zend/ZEND_CHANGES
+++ b/Zend/ZEND_CHANGES
@@ -26,11 +26,11 @@ Changes in the Zend Engine 2.0
occurs, in order to allow developers to gradually migrate to the
version 2.0-style behavior (without automatic clones).
- * delete function.
+ * delete statement.
The Zend Engine 1.0 had no means to force deletion of an object
if there are still references to it. The newly introduced delete
- function calls the object’s destructor and frees it even if the
+ statement calls the object’s destructor and frees it even if the
object is referenced by some other places in the engine. Other
references to the deleted object become stale and trying to
access them results in a fatal error.