<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/php-git.git/ext/tokenizer/tests, branch php-7.3.20</title>
<subtitle>git.php.net: repository/php-src.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/'/>
<entry>
<title>Sync leading and final newlines in *.phpt sections</title>
<updated>2018-10-15T02:32:30+00:00</updated>
<author>
<name>Peter Kokot</name>
<email>peterkokot@gmail.com</email>
</author>
<published>2018-10-15T02:32:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=b746e6988743b46ccb0542d5d568eef0608ee296'/>
<id>b746e6988743b46ccb0542d5d568eef0608ee296</id>
<content type='text'>
This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

According to POSIX, a line is a sequence of zero or more non-' &lt;newline&gt;'
characters plus a terminating '&lt;newline&gt;' character. [1] Files should
normally have at least one final newline character.

C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."

Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch adds missing newlines, trims multiple redundant final
newlines into a single one, and trims redundant leading newlines in all
*.phpt sections.

According to POSIX, a line is a sequence of zero or more non-' &lt;newline&gt;'
characters plus a terminating '&lt;newline&gt;' character. [1] Files should
normally have at least one final newline character.

C89 [2] and later standards [3] mention a final newline:
"A source file that is not empty shall end in a new-line character,
which shall not be immediately preceded by a backslash character."

Although it is not mandatory for all files to have a final newline
fixed, a more consistent and homogeneous approach brings less of commit
differences issues and a better development experience in certain text
editors and IDEs.

[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206
[2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2
[3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
</pre>
</div>
</content>
</entry>
<entry>
<title>Trim trailing whitespace in *.phpt</title>
<updated>2018-10-14T17:45:12+00:00</updated>
<author>
<name>Peter Kokot</name>
<email>peterkokot@gmail.com</email>
</author>
<published>2018-10-14T15:45:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=782352c54ad69c517e3c32b0dd2c25d74842647a'/>
<id>782352c54ad69c517e3c32b0dd2c25d74842647a</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed bug #76991</title>
<updated>2018-10-10T13:00:18+00:00</updated>
<author>
<name>Nikita Popov</name>
<email>nikita.ppv@gmail.com</email>
</author>
<published>2018-10-10T12:57:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=01948f20b8ae8eed252177f63bf2c9c11a8f1b94'/>
<id>01948f20b8ae8eed252177f63bf2c9c11a8f1b94</id>
<content type='text'>
Back up exceptions while the scan-ahead loop, to avoid an early
bail out.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Back up exceptions while the scan-ahead loop, to avoid an early
bail out.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed bug #76538</title>
<updated>2018-06-27T21:06:25+00:00</updated>
<author>
<name>Nikita Popov</name>
<email>nikita.ppv@gmail.com</email>
</author>
<published>2018-06-27T21:06:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=9b02ee0bba86becc951b65bb6d3527cf3ba7265e'/>
<id>9b02ee0bba86becc951b65bb6d3527cf3ba7265e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fixed bug #76437 (token_get_all with TOKEN_PARSE flag fails to recognise close tag)</title>
<updated>2018-06-18T03:33:48+00:00</updated>
<author>
<name>Xinchen Hui</name>
<email>laruence@gmail.com</email>
</author>
<published>2018-06-18T03:33:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=4d69bbeee79c6a94348935ad071b6c7c05dd8eae'/>
<id>4d69bbeee79c6a94348935ad071b6c7c05dd8eae</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Implement flexible heredoc/nowdoc syntax</title>
<updated>2018-04-13T19:35:37+00:00</updated>
<author>
<name>Thomas Punt</name>
<email>tpunt@hotmail.co.uk</email>
</author>
<published>2017-09-15T13:07:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=4887357269107ed669463c4b95bd755fbbb52490'/>
<id>4887357269107ed669463c4b95bd755fbbb52490</id>
<content type='text'>
RFC: https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes

* The ending label no longer has to be followed by a semicolon or
  newline. Any non-label character is fine.
* The ending label may be indented. The indentation will be stripped
  from all lines in the heredoc/nowdoc string.

Lexing of heredoc strings performs a scan-ahead to determine the
indentation of the ending label, so that the correct amount of
indentation can be removed when calculting the semantic values for
use by the parser. This makes the implementation quite a bit more
complicated than we would like :/
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
RFC: https://wiki.php.net/rfc/flexible_heredoc_nowdoc_syntaxes

* The ending label no longer has to be followed by a semicolon or
  newline. Any non-label character is fine.
* The ending label may be indented. The indentation will be stripped
  from all lines in the heredoc/nowdoc string.

Lexing of heredoc strings performs a scan-ahead to determine the
indentation of the ending label, so that the correct amount of
indentation can be removed when calculting the semantic values for
use by the parser. This makes the implementation quite a bit more
complicated than we would like :/
</pre>
</div>
</content>
</entry>
<entry>
<title>Revert "Handle scanner error in first place (don't hide them from ext/tokenizer) and cheaper whitespace handlig."</title>
<updated>2018-03-13T22:08:03+00:00</updated>
<author>
<name>Dmitry Stogov</name>
<email>dmitry@zend.com</email>
</author>
<published>2018-03-13T22:08:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=d1585a9e3f7c6e3da7177f07c68b250543d8fbf2'/>
<id>d1585a9e3f7c6e3da7177f07c68b250543d8fbf2</id>
<content type='text'>
This reverts commit 0d6da03f5c3e49b92cf6817ba8a7f8d6f60ee1aa.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This reverts commit 0d6da03f5c3e49b92cf6817ba8a7f8d6f60ee1aa.
</pre>
</div>
</content>
</entry>
<entry>
<title>Handle scanner error in first place (don't hide them from ext/tokenizer) and cheaper whitespace handlig.</title>
<updated>2018-03-13T15:42:09+00:00</updated>
<author>
<name>Dmitry Stogov</name>
<email>dmitry@zend.com</email>
</author>
<published>2018-03-13T15:42:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=0d6da03f5c3e49b92cf6817ba8a7f8d6f60ee1aa'/>
<id>0d6da03f5c3e49b92cf6817ba8a7f8d6f60ee1aa</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Use EXPECT instead of EXPECTF when possible</title>
<updated>2018-02-20T20:53:48+00:00</updated>
<author>
<name>Gabriel Caruso</name>
<email>carusogabriel34@gmail.com</email>
</author>
<published>2018-02-19T08:59:41+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=ded3d984c6133b1f508ed84e96df3316e207c99b'/>
<id>ded3d984c6133b1f508ed84e96df3316e207c99b</id>
<content type='text'>
EXPECTF logic in run-tests.php is considerable, so let's avoid it.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
EXPECTF logic in run-tests.php is considerable, so let's avoid it.
</pre>
</div>
</content>
</entry>
<entry>
<title>Use int instead of integer in type errors</title>
<updated>2018-02-04T18:08:23+00:00</updated>
<author>
<name>Gabriel Caruso</name>
<email>carusogabriel34@gmail.com</email>
</author>
<published>2018-02-04T13:33:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/php-git.git/commit/?id=ce1d69a1f6dcf15d43029301059c25e5bc09a577'/>
<id>ce1d69a1f6dcf15d43029301059c25e5bc09a577</id>
<content type='text'>
PHP requires integer typehints to be written "int" and does not
allow "integer" as an alias. This changes type error messages to
match the actual type name and avoids confusing messages like
"must be of the type integer, integer given".
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
PHP requires integer typehints to be written "int" and does not
allow "integer" as an alias. This changes type error messages to
match the actual type name and avoids confusing messages like
"must be of the type integer, integer given".
</pre>
</div>
</content>
</entry>
</feed>
