Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82370
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.179 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <CABBJUpdCgbBkG_WCM=reC9opFYWVCQU0CHJ7b7c1c=YYTJ_yjA@mail.gmail.com>
References: <CAEZPtU6yorwRtoC1zMiEMrvuB_+ijL+UOBNZ-YJHxFGanw+UXg@mail.gmail.com>
	<CABBJUpdqU=EvaZuYyp4=HxaM=uCw5drjxa_u6qqVR1bJSzeyMQ@mail.gmail.com>
	<CAEZPtU6pdCD-_0O3Xg8+YsbtbE4NHGS7q0EAewm8UBBY2B2_uw@mail.gmail.com>
	<CABBJUpdqiSNvqPcVQXyLmuJapphPDsSQDHHY2CJjZ7uinpAx6w@mail.gmail.com>
	<a82346245b54159f2b30061b9f200c39.squirrel@webmail.klapt.com>
	<CAEKnhAH7ctCOc+TcR+znTxhieGocWHXXKrtWH-0-27dsKyh1yQ@mail.gmail.com>
	<CAEZPtU5y6QH50yvNtH_R5GuJCtBwzpFKusQKS1s6sxBBWayUPw@mail.gmail.com>
	<CAEKnhAHLdN26ZayD6bXLWxBdebLhBnHR25QMpS1wqToev7F_+g@mail.gmail.com>
	<CABBJUpdCgbBkG_WCM=reC9opFYWVCQU0CHJ7b7c1c=YYTJ_yjA@mail.gmail.com>
Date: Tue, 10 Feb 2015 11:56:09 +0000
Message-ID: <CAEKnhAH5PnDhAW1LPGi6T25FA-Js8YkbBpK2HGxR4TktpnJ=tw@mail.gmail.com>
To: Xinchen Hui <laruence@php.net>
Cc: Pierre Joye <pierre.php@gmail.com>, Anatol Belski <anatol.php@belski.net>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113fc1ec910812050eba9218
Subject: Re: [PHP-DEV] new json, push generated file?
From: bukka@php.net (Jakub Zelenka)

--001a113fc1ec910812050eba9218
Content-Type: text/plain; charset=UTF-8

Hey

On Tue, Feb 10, 2015 at 2:47 AM, Xinchen Hui <laruence@php.net> wrote:
>
> why make this thing in this way complicated? why not just simply
> include the generated files as others did?


First of all the others did exactly what I have already done. :) It means
they included re2c generated files and did not include bison generated
files.

There are few reasons why I would like to do it slightly differently in
json and make the re-generation optional.

1. I want to prevent an accidental re-generation of files with the old
version of re2c and bison. It happens to me from time to time when I switch
branches and build often. Then I see that I have changes (git diff) in the
zend_language_scanner.c and other re2c generated files even if I haven't
edited them. The reason is because the version that I use is different and
the files got regenerated (you won't see that if you use the same version).
That could be even bigger problem with bison where the the version
differences are much more often.

2. As soon as I start using new features (like utf8 ranges in re2c) that
are not available in the old version and someone would try to do some
changes in the scanner and regenerate it, then it would fail with error. I
believe that it's better if the user gets a warning during the
configuration and the compilation exits the build instead of generating an
error.

3 It is sort of a signal which version is currently supported and it
hopefully prevents things like regenerating files with the old version and
pushing it to the repo (as Anatol did yesterday in
https://github.com/php/php-src/commit/89893541305594eba373c15156eb54d7a7cb5960
).


As I said in the PR. This change won't affect anyone who doesn't change
json scanner and parser which is 99% of all users that build PHP. The 1% is
probably just me so it's not really complicated IMHO...

I would also like to add all of this to the json README (it's very outdated
and I plan to update it anyway) and possibly other build doc if we have any.

Cheers

Jakub

--001a113fc1ec910812050eba9218--