Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92770 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39909 invoked from network); 26 Apr 2016 08:38:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Apr 2016 08:38:25 -0000 Authentication-Results: pb1.pair.com header.from=lisachenko.it@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lisachenko.it@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender) X-PHP-List-Original-Sender: lisachenko.it@gmail.com X-Host-Fingerprint: 209.85.215.44 mail-lf0-f44.google.com Received: from [209.85.215.44] ([209.85.215.44:33589] helo=mail-lf0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C1/8B-02401-FF82F175 for ; Tue, 26 Apr 2016 04:38:25 -0400 Received: by mail-lf0-f44.google.com with SMTP id y84so8090872lfc.0 for ; Tue, 26 Apr 2016 01:38:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=bh9VNM1eB/+FulMU4WOya8hg1RHrm0cDpWuUPLCBrv0=; b=KaezjdFmfWcxkNOI3SEOECUgS8+9kknalcfvGI/pfj5SNTcQfdIjeY9qR1Uyj39E+V s5CmCALdiAj3gvHpr9mNIrKulGNA3mubAwmdJ5gA0u3foUPapXSapUbPdOA/qiH5GAwT Z3McL18G+38DENOUgCtFUZWiEbm2pdAi5FoqqIZeu0ZR7c3mDpDucNWWFJ8HmeK4kXRN HOtZb3aSiGHKBTME9SdioauKM38SDkvBQAWIi7W2Y48YojPfwDh78SzzNldnIIPAO0qI EHtaTBeJcIqi5a7AHHXpve4+n1LbhUHW4ufmSNbWUexdwdV0WEF56oo4UkuHvef13jct nKsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=bh9VNM1eB/+FulMU4WOya8hg1RHrm0cDpWuUPLCBrv0=; b=LEuORC9YwBurIOtvi2IcOA73Jm2JQhTywOTEruhZpQvKyJdT8nuEFFxHFyZpXwq4p3 n6fqoAVio0jrExUn8gcVRgH42tEM3gtR8nYqU1z8lxF/6G36b5oea46ciU4bWI+vpviv 9/uKavBBmEVQuYapJqnk6KkEpvxgDvxabSKvOMEmztkndJzABDx0nqFVZc4Pq2PnNAZt WjOB0V2zKwfJFygqlf+VdOm4UZum1AusnBrzcmMyccI/Hix0lCgyTKhEKIeuRBpd2aDx uGz+LbY57uNDCbC9LJXkXIEm/N5bIarHwiQggA2dpJJrwlKnVBkNtEZG/QYgTg+hPAkD +cJQ== X-Gm-Message-State: AOPr4FUda5EvkdvFqfBYYaXHI/UV736Vp3iYw2bTcpWdXIH109vGYvnxiDbsVqJlh6c4Ik5Wl4ZOZggRWweZrw== MIME-Version: 1.0 X-Received: by 10.112.169.105 with SMTP id ad9mr720858lbc.123.1461659901227; Tue, 26 Apr 2016 01:38:21 -0700 (PDT) Received: by 10.25.218.65 with HTTP; Tue, 26 Apr 2016 01:38:21 -0700 (PDT) In-Reply-To: References: Date: Tue, 26 Apr 2016 11:38:21 +0300 Message-ID: To: Nikita Popov Cc: Leigh , Sara Golemon , Nikita Popov , PHP internals list Content-Type: multipart/alternative; boundary=001a11c38c0831ff1505315f3785 Subject: Re: [PHP-DEV] [RFC][Discussion] Parser extension API From: lisachenko.it@gmail.com (Alexander Lisachenko) --001a11c38c0831ff1505315f3785 Content-Type: text/plain; charset=UTF-8 2016-04-26 11:15 GMT+03:00 Nikita Popov : > As an update here, I plan to create an RFC for bundling the php-ast > extension (maybe with minor modifications) with php-src. This was planned > for 7.1 anyway, and with the annotations RFC under discussion, this seems > like a good time. > ... > I'll try to post an RFC for review this week. > Hello, Nikita! It's a great news! Having this stuff in the 7.1 core is awesome! But I have several petitions for this API: 1) Could it avoid using of raw functions for parsing API, like ast\parse_file or ast\parse_code 2) Could you please put all the parsing stuff into the `Parser` class and put it into the `Php\` namespace, as well with node classes? --001a11c38c0831ff1505315f3785--