summaryrefslogtreecommitdiff
path: root/ext/xsl/tests
Commit message (Collapse)AuthorAgeFilesLines
* Promote warnings in ext/xslNikita Popov2020-09-282-4/+24
|
* Run tidyNikita Popov2020-09-184-9/+9
| | | | | This should fix most of the remaining issues with tabs and spaces being mixed in tests.
* Improve error messages mentioning parameters instead of argumentsMáté Kocsis2020-09-091-1/+1
| | | | Closes GH-5999
* Move custom type checks to ZPPMáté Kocsis2020-09-021-7/+10
| | | | Closes GH-6034
* Add many missing closing PHP tags to testsMáté Kocsis2020-08-0924-0/+24
| | | | Closes GH-5958
* Make exit() unwind properlyNikita Popov2020-06-291-1/+0
| | | | | | | | | | | exit() is now internally implemented by throwing an exception, performing a normal stack unwind and a clean shutdown. This ensures that no persistent resource leaks occur. The exception is internal, cannot be caught and does not result in the execution of finally blocks. This may be relaxed in the future. Closes GH-5768.
* Avoid warning on exception in xsl extNikita Popov2020-06-252-2/+43
|
* Test XSLTProcessor::importStylesheet() with invalid stylesheetSymeon Charalabides2020-04-241-0/+19
|
* Perform some maintenance work on the XSL extensionMáté Kocsis2020-03-101-2/+6
| | | | | Added stubs, fixed some ZPP, and changed PHP_FALIASes to PHP_METHODs. Closes GH-5241
* Reindent phpt filesNikita Popov2020-02-035-36/+36
|
* Merge branch 'PHP-7.4'Christoph M. Becker2020-01-301-0/+51
|\ | | | | | | | | * PHP-7.4: Fix #70078: XSL callbacks with nodes as parameter leak memory
| * Merge branch 'PHP-7.3' into PHP-7.4Christoph M. Becker2020-01-301-0/+51
| |\ | | | | | | | | | | | | * PHP-7.3: Fix #70078: XSL callbacks with nodes as parameter leak memory
| | * Fix #70078: XSL callbacks with nodes as parameter leak memoryChristoph M. Becker2020-01-301-0/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | The fix for bug #49634 solved a double-free by copying the node with `xmlDocCopyNodeList()`, but the copied node is later freed by calling `xmlFreeNode()` instead of `xmlFreeNodeList()`, thus leaking memory. However, there is no need to treat the node as node list, i.e. to copy also the node's siblings; just creating a recursive copy of the node with `xmlDocCopyNode()` is sufficient, while that also avoids the leak.
| | * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1535-49/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-' <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
| | * Trim trailing whitespace in *.phptPeter Kokot2018-10-1425-48/+48
| | |
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-143-5/+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
* | | Merge branch 'PHP-7.4'Nikita Popov2020-01-211-5/+5
|\ \ \ | |/ / | | | | | | | | | * PHP-7.4: Fix file clash in bug54446.phpt tests
| * | Fix file clash in bug54446.phpt testsNikita Popov2020-01-211-5/+5
| | |
* | | Fix #78880: Final spelling fixesMáté Kocsis2020-01-161-2/+2
| | |
* | | Clean DONE tags from testsFabien Villepinte2019-11-071-2/+0
|/ / | | | | | | | | | | | | Remove most of the `===DONE===` tags and its variations. Keep `===DONE===` if the test output otherwise becomes empty. Closes GH-4872.
* | Set up asan+ubsan scheduled build on azureNikita Popov2019-06-281-1/+4
| | | | | | | | | | | | | | | | | | Also adds an --asan flag to run-tests.php to setup all the necessary environment variables. Some tests are marked as skipped because they are incompatible with asan or too slow. I'm basing this on the DEBUG_ZTS build, which seems to give us the most mileage.
* | Replace dirname(__FILE__) by __DIR__ in testsFabien Villepinte2019-03-1534-62/+62
| |
* | Use EXPECT when possibleGabriel Caruso2019-03-111-1/+1
| | | | | | | | EXPECTF logic in run-tests.php is considerable, so let's avoid it.
* | Remove more zpp error testsNikita Popov2019-03-0517-879/+0
| |
* | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1535-49/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-' <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
* | Trim trailing whitespace in *.phptPeter Kokot2018-10-144-14/+14
| |
* | Trim trailing whitespace in testsGabriel Caruso2018-10-1423-34/+34
| |
* | Sync leading and final newlines in source code filesPeter Kokot2018-10-143-5/+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
* Remove old SVN keywords substitutions from xsl and sockets testsPeter Kokot2018-06-138-8/+0
| | | | | | | | When the PHP source code was versioned in Subversion, there was possible to substitute certain keywords such as $Id$ with revision number, last change time and author name. Such approach is not used in Git so this patch removes these outdated artifacts from the xsl and sockets extensions tests files.
* remove support for string|unicode in testsGabriel Caruso2018-02-221-1/+1
|
* Use EXPECT instead of EXPECTF when possibleGabriel Caruso2018-02-2011-11/+11
| | | | EXPECTF logic in run-tests.php is considerable, so let's avoid it.
* Use bool instead of boolean while throwing a type errorGabriel Caruso2018-02-043-3/+3
| | | | | | | | | | PHP requires boolean typehints to be written "bool" and disallows "boolean" as an alias. This changes the error messages to match the actual type name and avoids confusing messages like "must be of type boolean, boolean given". This a followup to ce1d69a1f6dcf15d43029301059c25e5bc09a577, which implements the same change for integer->int.
* Add and fix SKIPIF sectionsGabriel Caruso2018-02-041-13/+0
|
* Use %d when expecting line number in testsGabriel Caruso2018-02-0215-17/+17
|
* Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2017-09-112-0/+207
|\ | | | | | | | | * PHP-7.1: Fork test to keep up with libxsl >= 1.1.30
| * Merge branch 'PHP-7.0' into PHP-7.1Anatol Belski2017-09-112-0/+207
| |\ | | | | | | | | | | | | * PHP-7.0: Fork test to keep up with libxsl >= 1.1.30
| | * Fork test to keep up with libxsl >= 1.1.30Anatol Belski2017-09-112-0/+207
| | | | | | | | | | | | | | | | | | The behavior of date parsing has changed and is reflected in the changelog. Invalid dates are not accepted, in particular dates with a negative year, as in this test.
* | | Deprecate __autoload()Nikita Popov2017-02-031-2/+2
| | |
* | | Remove more PHP 6 leftovers from testsNikita Popov2016-11-242-4/+4
|/ /
* | Fixed the UTF-8 and long path support in the streams on Windows.Anatol Belski2016-06-202-0/+37
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since long the default PHP charset is UTF-8, however the Windows part is out of step with this important point. The current implementation in PHP doesn't technically permit to handle UTF-8 filepath and several other things. Till now, only the ANSI compatible APIs are being used. Here is more about it https://msdn.microsoft.com/en-us/library/windows/desktop/dd317752%28v=vs.85%29.aspx The patch fixes not only issues with multibyte filenames under incompatible codepages, but indirectly also issues with some other multibyte encodings like BIG5, Shift-JIS, etc. by providing a clean way to access filenames in UTF-8. Below is a small list of issues from the bug tracker, that are getting fixed: https://bugs.php.net/63401 https://bugs.php.net/41199 https://bugs.php.net/50203 https://bugs.php.net/71509 https://bugs.php.net/64699 https://bugs.php.net/64506 https://bugs.php.net/30195 https://bugs.php.net/65358 https://bugs.php.net/61315 https://bugs.php.net/70943 https://bugs.php.net/70903 https://bugs.php.net/63593 https://bugs.php.net/54977 https://bugs.php.net/54028 https://bugs.php.net/43148 https://bugs.php.net/30730 https://bugs.php.net/33350 https://bugs.php.net/35300 https://bugs.php.net/46990 https://bugs.php.net/61309 https://bugs.php.net/69333 https://bugs.php.net/45517 https://bugs.php.net/70551 https://bugs.php.net/50197 https://bugs.php.net/72200 https://bugs.php.net/37672 Yet more related tickets can for sure be found - on bugs.php.net, Stackoverflow and Github. Some of the bugs are pretty recent, some descend to early 2000th, but the user comments in there last even till today. Just for example, bug #30195 was opened in 2004, the latest comment in there was made in 2014. It is certain, that these bugs descend not only to pure PHP use cases, but get also redirected from the popular PHP based projects. Given the modern systems (and those supported by PHP) are always based on NTFS, there is no excuse to keep these issues unresolved. The internalization approach on Windows is in many ways different from UNIX and Linux, while it supports and is based on Unicode. It depends on the current system code page, APIs used and exact kind how the binary was compiled The locale doesn't affect the way Unicode or ANSI API work. PHP in particular is being compiled without _UNICODE defined and this is conditioned by the way we handle strings. Here is more about it https://msdn.microsoft.com/en-us/library/tsbaswba.aspx However, with any system code page ANSI functions automatically convert paths to UTF-16. Paths in some encodings incompatible with the current system code page, won't work correctly with ANSI APIs. PHP till now only uses the ANSI Windows APIs. For example, on a system with the current code page 1252, the paths in cp1252 are supported and transparently converted to UTF-16 by the ANSI functions. Once one wants to handle a filepath encoded with cp932 on that particular system, an ANSI or a POSIX compatible function used in PHP will produce an erroneous result. When trying to convert that cp932 path to UTF-8 and passing to the ANSI functions, an ANSI function would likely interpret the UTF-8 string as some string in the current code page and create a filepath that represents every single byte of the UTF-8 string. These behaviors are not only broken but also disregard the documented INI settings. This patch solves the issies with the multibyte paths on Windows by intelligently enforcing the usage of the Unicode aware APIs. For functions expect Unicode (fe CreateFileW, FindFirstFileW, etc.), arguments will be converted to UTF-16 wide chars. For functions returning Unicode aware data (fe GetCurrentDirectoryW, etc.), resulting wide string is converted back to char's depending on the current PHP charset settings, either to the current ANSI codepage (this is the behavior prior to this patch) or to UTF-8 (the default behavior). In a particular case, users might have to explicitly set internal_encoding or default_charset, if filenames in ANSI codepage are necessary. Current tests show no regressions and witness that this will be an exotic case, the current default UTF-8 encoding is compatible with any supported system. The dependency libraries are long switching to Unicode APIs, so some tests were also added for extensions not directly related to streams. At large, the patch brings over 150 related tests into the core. Those target and was run on various environments with European, Asian, etc. codepages. General PHP frameworks was tested and showed no regressions. The impact on the current C code base is low, the most places affected are the Windows only places in the three files tsrm_win32.c, zend_virtual_cwd.c and plain_wrapper.c. The actual implementation of the most of the wide char supporting functionality is in win32/ioutil.* and win32/codepage.*, several low level functionsare extended in place to avoid reimplementation for now. No performance impact was sighted. As previously mentioned, the ANSI APIs used prior the patch perform Unicode conversions internally. Using the Unicode APIs directly while doing custom conversions just retains the status quo. The ways to optimize it are open (fe. by implementing caching for the strings converted to wide variants). The long path implementation is user transparent. If a path exceeds the length of _MAX_PATH, it'll be automatically prefixed with \\?\. The MAXPATHLEN is set to 2048 bytes. Appreciation to Pierre Joye, Matt Ficken, @algo13 and others for tips, ideas and testing. Thanks.
* Merge branch 'PHP-5.6' into PHP-7.0Anatol Belski2016-03-141-1/+2
|\ | | | | | | | | * PHP-5.6: fix test
| * fix testAnatol Belski2016-03-141-1/+2
| | | | | | | | | | Many warnings won't appear with libxml2 >= 2.9.3 because in many cases libxml2 2.9.3 will just abort processing.
| * Fix bug #71540 - NULL pointer dereference in xsl_ext_function_php()Stanislav Malyshev2016-02-151-0/+67
| |
* | More fixing for bug #71540Stanislav Malyshev2016-02-151-0/+2
| |
* | Fix bug #71540 - NULL pointer dereference in xsl_ext_function_php()Stanislav Malyshev2016-02-151-0/+67
| |
* | Use dieXinchen Hui2015-09-201-2/+2
| |
* | Fixed bug #70535 (XSLT: free(): invalid pointer)Xinchen Hui2015-09-201-0/+22
| |
* | Tweak uncaught exception message displayNikita Popov2015-05-171-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | This implements a reduced variant of #1226 with just the following change: -Fatal error: Uncaught exception 'EngineException' with message 'Call to private method foo::bar() from context ''' in %s:%d +Fatal error: Uncaught EngineException: Call to private method foo::bar() from context '' in %s:%d The '' wrapper around messages is very weird if the exception message itself contains ''. Futhermore having the message wrapped in '' doesn't work for the "and defined" suffix of TypeExceptions.
* | Finish PHP 4 constructor deprecationNikita Popov2015-03-311-1/+1
| |
* | Remove xsl.security_prefs ini optionNikita Popov2015-03-091-45/+5
|/ | | | | | Conflicts: ext/xsl/php_xsl.c ext/xsl/xsltprocessor.c
View Lorry Controller Status