Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.lang.php Subject: Re: parsing print_r() output with preg_match_all() Date: Thu, 14 Jan 2016 10:24:42 +1300 Lines: 22 Message-ID: References: <568d3dcf$0$23748$e4fe514c@news.xs4all.nl> <87r3huzevd.fsf@bsb.me.uk> <568d6f9c$0$23759$e4fe514c@news.xs4all.nl> <569363A3.6040108@arnowelzel.de> <5694313D.3060100@arnowelzel.de> <6929015.zlp62RpN2j@PointedEars.de> <569483AF.6010606@arnowelzel.de> <56956576.3040909@arnowelzel.de> <56956FF5.3050603@arnowelzel.de> <5695E316.9050809@arnowelzel.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net YPknCLOiVoOnQDhpFXxLmQstKk7PyYSkrcJUeMQpJ0h7bolgqZ Cancel-Lock: sha1:LEQKeX7xbxk+zSeYJdlDwbQk7uM= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Xref: csiph.com comp.lang.php:16251 Jerry Stuckle wrote: > On 1/13/2016 12:39 AM, Arno Welzel wrote: >> It seems you really don't understand what I'm talking about. I mentioned >> JSON as a human readable standard instead of using var_dump() since >> var_dump() is not meant to be parsed. Then you said that I don't know >> what a standard is and that JSON is not "human readable". I even believe >> you don't know what "human readable" really means. Hint: the numbers >> above an GTIN-13 bar code are "human readable" even if you don't know >> what they mean - but at least you can read them in case the barcode >> reader does not work. > > Sure, I know what JSON is all about, troll. But no matter how you cut > it, you can create XML much more human readable than JSON. But you've > never done anything with XML, so you have no idea what it's about. The hypervisor OS I use uses JSON for all of its configuration and status output. It's clearly an easy format for both normal humans and machines to read. -- Ian Collins