Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103720 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 62223 invoked from network); 12 Jan 2019 23:43:46 -0000 Received: from unknown (HELO vie01a-dmta-pe06-1.mx.upcmail.net) (84.116.36.14) by pb1.pair.com with SMTP; 12 Jan 2019 23:43:46 -0000 Received: from [172.31.216.235] (helo=vie01a-pemc-psmtp-pe12.mail.upcmail.net) by vie01a-dmta-pe06.mx.upcmail.net with esmtp (Exim 4.88) (envelope-from ) id 1giPkA-0002az-0P for internals@lists.php.net; Sat, 12 Jan 2019 21:18:58 +0100 Received: from mail02.home ([213.47.8.56]) by vie01a-pemc-psmtp-pe12.mail.upcmail.net with ESMTP id iPjBgPDps2WSsiPjBgKUV0; Sat, 12 Jan 2019 21:17:58 +0100 X-Env-Mailfrom: markus@fischer.name X-Env-Rcptto: internals@lists.php.net X-SourceIP: 213.47.8.56 X-CNFS-Analysis: v=2.3 cv=E7kcWpVl c=1 sm=1 tr=0 a=UsP8JIz990cEySE/ILGzbQ==:117 a=UsP8JIz990cEySE/ILGzbQ==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=3JhidrIBZZsA:10 a=2EALvoLjsrEA:10 a=ZZnuYtJkoWoA:10 a=Ekg2NFr5KlXMjpJfGjYA:9 a=QEXdDO2ut3YA:10 Received: from mail02.home ([192.168.1.14] helo=[IPv6:::1]) by mail02.home with esmtp (Exim 4.72) (envelope-from ) id 1giPjA-0001rs-Rb for internals@lists.php.net; Sat, 12 Jan 2019 21:17:57 +0100 To: internals@lists.php.net References: Message-ID: <10f8dab1-7ee0-e949-a39d-2248a607f1e6@fischer.name> Date: Sat, 12 Jan 2019 21:21:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "scanner01.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On 12.01.19 21:13, Dan Ackroyd wrote: > Hi Duncan, [...] great points I was about to reply to Craig when Dans' email hit the list. I couldn't agree with Dan more. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-CMAE-Envelope: MS4wfPqfVsWNUcP2grLYxWCBNuwVEO/PgC87XCeZJz6Oxfx18MO4dpGt/ULh5BWUj+sul2EsBRLfGYTreKLy+pKaRluew3SACFBr35Bga8zahnxsyVLfq++d ROZaD/emTaivfkfSXl4B/rmkegTzeq1AeSVBOehZtjLQTI01Rd4dKRk+ Subject: Re: [PHP-DEV] Making stdClass iterable From: markus@fischer.name (Markus Fischer) On 12.01.19 21:13, Dan Ackroyd wrote: > Hi Duncan, [...] great points I was about to reply to Craig when Dans' email hit the list. I couldn't agree with Dan more. The expanded use of stdClass feels wrong to me, as in: wrong solution to a problem best solved differently. Dan gave ample examples about that. I think one more approach not mentioned is that you could also `(array) $yourStdClassVar`. Of course you didn't ask for it, but nevertheless: stdClass is already a weird thing on its own and I wouldn't want to see it getting more attention to increase the encourage to use it. cheers, - Markus