Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109783 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53992 invoked from network); 22 Apr 2020 19:05:55 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 22 Apr 2020 19:05:55 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 43A691804C2 for ; Wed, 22 Apr 2020 10:37:37 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS8075 40.64.0.0/10 X-Spam-Virus: No X-Envelope-From: Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12olkn2061.outbound.protection.outlook.com [40.92.21.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 22 Apr 2020 10:37:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZymRvNwJfDAXeKRhzdDV6qpCjyRZN3TJqaM6vMdcMr1xIXORmTC1kDWPfH78oaOiV/89nktXvHEzRNjekVVCFCwIjOvmmUtyjiS6jMWsuxnTRNN79NN4VwykSEKKU+DoXB63ngclduBU+oYoFM7EAQFYgB/zNueSgqNr1FZQAuPxKk7hoacIhrxGKu4LEUVOkmWSBIxWrdNMFGQIHJM2weTaH/bPSiNcahi3J0u0Dodft4WpldF3vG01bsi+iUgYB0Qelz0nt4FYzkS2VywMKznkhwqvaIfSCtPpejc8B+HXf5vfDu2ShG7UcPSPGnNnfrZJuMKzIgGBscPbAVW5BQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c6x9EhB6SDTxBzZm58jNtKGlGoReHOpfBOnl09pWJGU=; b=kBlHpH1w14gWqMKSEpByLb2sG5hvrFAEjFpU22FE9RhEkSuKuSvCzyi80a9nUNZzrT3YL1rEZrfq/TQ/gbLtD1C155V/cuxG9ToasgUnmJHIhYNG5icmz5GEzVlHxzGPsquyCLM6QeEByU7iZCC8zDiBN9sQOoDKveTKXVQicaS6OyfbE9+KpIHPV9aYbq0v7IZctB3vEr06GwieiqUNVtDdGad4NGrbuvwOzbniYdmT/IoI7JUWGd3ot1EbUuqVNybhPB4YpdXwsuEt9yfpQ7nm/nP8InehYoZJw4/abtqqYkel75Dtu7s4h3PRidpxsKnrp8QPxqAeBdWsR1F9yA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=c6x9EhB6SDTxBzZm58jNtKGlGoReHOpfBOnl09pWJGU=; b=ncPscu2n8xd8JGGgLlmd2EpoFpkzZh4p7Tfg0xO8xhxfSyNcpYeG6RyBYobkXvw72GyxgpWj28xYiHB6le7Ys4HNgEM1Pnux7N3T0t0vlj4VbxoISekg8r8VX174J/SnyW+hjrUmfTfSw2wL2oM9ycpMnti2qbbmfa4Ixn1uxsYdFCof/SKr/uIBv4bzLZ3Zz825KqvFnD9JO88PGGXALtXp1xlLJC63/T+NFOnzJzB44mM0ayUVUHjaKwv+/MeLKdGR/CHf3aRxl5WDSTeCgK+F1WMPpg9kHyKncSImYUEGxOWTJbPZJYKaqyoZx3arzqlVZCg/vhChZa/oVessVA== Received: from DM6NAM12FT039.eop-nam12.prod.protection.outlook.com (2a01:111:e400:fc64::4e) by DM6NAM12HT095.eop-nam12.prod.protection.outlook.com (2a01:111:e400:fc64::412) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.12; Wed, 22 Apr 2020 17:37:34 +0000 Received: from DM6PR07MB6618.namprd07.prod.outlook.com (2a01:111:e400:fc64::4b) by DM6NAM12FT039.mail.protection.outlook.com (2a01:111:e400:fc64::315) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.12 via Frontend Transport; Wed, 22 Apr 2020 17:37:34 +0000 Received: from DM6PR07MB6618.namprd07.prod.outlook.com ([fe80::e553:b74f:bf64:30c5]) by DM6PR07MB6618.namprd07.prod.outlook.com ([fe80::e553:b74f:bf64:30c5%4]) with mapi id 15.20.2921.030; Wed, 22 Apr 2020 17:37:34 +0000 To: Internals Thread-Topic: Moving json extension to core? Thread-Index: AQHWGMqhxOroEd7sC06MH32wx0DkhQ== Date: Wed, 22 Apr 2020 17:37:34 +0000 Message-ID: Accept-Language: en-CA, en-US Content-Language: en-CA X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:DBD0CD059F36FEA0EFCFD262E42E40102D5A35362BC7AAFBC80D56BBA16AA4DA;UpperCasedChecksum:D3C8BDB0FF83D9C11E78E9062729F1416E8C6D77385E7A4A8B7BD620CDC13075;SizeAsReceived:6662;Count:42 x-tmn: [Wq+XASr8di4HP80w7gKNBU+s5ykcO2Ui] x-ms-publictraffictype: Email x-incomingheadercount: 42 x-eopattributedmessage: 0 x-ms-office365-filtering-correlation-id: 26d10b0c-81b5-4246-abb1-08d7e6e3d7cc x-ms-traffictypediagnostic: DM6NAM12HT095: x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: ofVg1JvNDgAy25BWNa64BXZBPejn1NEak+nf6HfGGGCKPT2ugTtC0/dw4h3oSPyx1KEcdNIR5m/z5kBuPUHyFKUVshvWZca4zEBrn9xWkQhRIgRcWS6O+pDZAmheuA/efwqaDYZW2IOlNXJD/ka8RrSwpdm8ANSBHJqGAJzn63nWmG7LW0Bu2rRB5lRuqO8YZ1n2+viXbxA2yanRkTbSnNmLiS78A88Z5GwPvXBpnRPkmrjK5THExgfPsyMM2OwE x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:0;SRV:;IPV:NLI;SFV:NSPM;H:DM6PR07MB6618.namprd07.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:;DIR:OUT;SFP:1901; x-ms-exchange-antispam-messagedata: h4g+ZvzkzZtLeazXxjXfhjEhOXgNNRtepmsS83SdI9RwnS8zNSPeu/wQWBuw7svzZDKBvJayt2gfTvy8UIeEafgDd/C5kLtZAySdiE1LGjk6eDb75FQo04DoOE+0vwG/pFGu/XLxHgxwJ6gdoMGwUA== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: 26d10b0c-81b5-4246-abb1-08d7e6e3d7cc X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2020 17:37:34.7824 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM12HT095 Subject: Moving json extension to core? From: tysonandre775@hotmail.com (tyson andre) Hi internals,=0A= =0A= Currently, it's possible to disable the json extension with `./configure --= disable-json`.=0A= However, JSON is widely used in many use cases - web sites, logging output,= and as a data format that can be used in CLI programs=0A= to share data with many applications and programming languages, so I'd pers= onally find it useful if it was always enabled.=0A= (e.g. to publish self-contained scripts that don't require polyfills or les= s readable var_export output)=0A= =0A= https://wiki.php.net/rfc/jsond mentions that=0A= =0A= > The current Json Parser in the json extension does not have a free licens= e which is a problem for many Linux distros.=0A= > This has been referenced at Bug #63520. That results in not packaging jso= n extension in the many Linux distributions.=0A= =0A= Starting in php 7.0, I'd assume licensing is no longer an issue (correct me= if I'm wrong). I don't see anything discussed in the RFC or a quick search= of email threads about making JSON impossible to disable.=0A= =0A= Doing this would also make some extensions more convenient to use (e.g. mem= cached with the json serializer, using json encoding for uses such as error= messages in miscellaneous extensions, etc.)=0A= =0A= P.S. What are your thoughts about adding additional conversion specifiers s= uch as %j or %v to PHP to call JSON with the default options.=0A= It's a feature similar to those I've seen in programming languages such as = golang - https://golang.org/pkg/fmt/#hdr-Printing=0A= =0A= - `printf("console.log("value from php", %j);\n", $value)`=0A= - `printf("Some command returned %j\n", $boolValue)`=0A= =0A= Thanks,=0A= - Tyson=