Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13705 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 605 invoked by uid 1010); 3 Nov 2004 12:32:57 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 97440 invoked from network); 3 Nov 2004 12:32:30 -0000 Received: from unknown (HELO mail.gmx.net) (213.165.64.20) by pb1.pair.com with SMTP; 3 Nov 2004 12:32:30 -0000 Received: (qmail 16249 invoked by uid 65534); 3 Nov 2004 12:32:29 -0000 Received: from 55.Red-213-4-20.pooles.rima-tde.net (EHLO [10.10.0.21]) (213.4.20.55) by mail.gmx.net (mp014) with SMTP; 03 Nov 2004 13:32:29 +0100 X-Authenticated: #12441595 Message-ID: <4188DEC8.5060309@gmx.net> Date: Wed, 03 Nov 2004 14:36:08 +0100 User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: serialize bug with array that references to itself? From: fmmarzoa@gmx.net ("Francisco M. Marzoa Alonso") Try this code:

The second array is expected to be exactly as $Arr, but it doesn't. This is the output for that code: array(1) { ["self"]=> array(1) { ["self"]=> *RECURSION* } } array(1) { ["self"]=> array(1) { ["self"]=> NULL } } As you can see the second array has a NULL value where the first one had a recursive reference. Can this be considered as a bug of PHP serialization system?