summaryrefslogtreecommitdiff
path: root/ext/phar/tests/tar/files/make_invalid_tar.php.inc
Commit message (Collapse)AuthorAgeFilesLines
* Reindent phpt filesNikita Popov2020-02-031-2/+2
|
* Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' 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
* - IS_UNICODE checks and conversionsSteph Fox2008-05-191-1/+1
| | | | | | - stub and creation file updates - far too many test updates to think about
* - it helps if you add the new files :)Steph Fox2008-02-121-0/+9