summaryrefslogtreecommitdiff
path: root/ext/enchant
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'PHP-7.3' into PHP-7.4Christoph M. Becker2020-02-281-10/+6
|\ | | | | | | | | * PHP-7.3: Fix #79311: enchant_dict_suggest() fails on big endian architecture
| * Fix #79311: enchant_dict_suggest() fails on big endian architectureChristoph M. Becker2020-02-281-10/+6
| | | | | | | | | | | | | | | | | | | | For obvious reasons, we must not assign a `size_t` value to an `int` variable using memcpy(). However, there is actually no need for the intermediate `n_sugg_st` here, if we use the proper types in the first place. A regression test is not necessary, because dict_suggest.phpt already exhibits the erroneous behavior on big endian architectures.
| * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-1422-83/+83
| |
| * Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Fix proto of enchant_broker_list_dicts()Fabien Villepinte2019-10-191-1/+1
| |
* | Show actual enchant version if possibleChristoph M. Becker2019-06-273-4/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | As of libenchant 1.6.0 there is enchant_get_version()[1], so we use it, if available, to show the actual enchant version in the PHP info. We also drop the fake ENCHANT_VERSION_STRING altogether, but stick with showing version 1.5.x if at least HAVE_ENCHANT_BROKER_SET_PARAM is defined. Future scope: we may consider requiring enchant 1.6.0 (or later), since this has been released in April 2010, and likely is available everywhere. [1] <https://www.abisource.com/projects/enchant/>
* | ext/enchant: Pass $ENCHANT_LIBS to PHP_CHECK_LIBRARY to fix shared buildsHugh McMaster2019-06-031-0/+2
| | | | | | | | Closes GH-4216.
* | enchant: fix shared buildRemi Collet2019-05-211-2/+3
| |
* | Use PKG_CHECK_MODULES to detect the Enchant libraryHugh McMaster2019-05-171-31/+13
| |
* | Normalize comments in *nix build system m4 filesPeter Kokot2019-05-121-2/+0
| | | | | | | | | | | | | | | | | | Normalization include: - Use dnl for everything that can be ommitted when configure is built in favor of the shell comment character # which is visible in the output. - Line length normalized to 80 columns - Dots for most of the one line sentences - Macro definitions include similar pattern header comments now
* | Cleanup unused module globalsDmitry Stogov2019-03-121-6/+0
| |
* | Add AS_HELP_STRING to *nix build configure optionsPeter Kokot2019-03-071-3/+4
| | | | | | | | | | | | | | | | The Autoconf's default AS_HELP_STRING macro can properly format help strings [1] so watching out if columns are aligned manually is not anymore. [1] https://www.gnu.org/software/autoconf/manual/autoconf.html#Pretty-Help-Strings
* | Remove local variablesPeter Kokot2019-02-032-18/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch removes the so called local variables defined per file basis for certain editors to properly show tab width, and similar settings. These are mainly used by Vim and Emacs editors yet with recent changes the once working definitions don't work anymore in Vim without custom plugins or additional configuration. Neither are these settings synced across the PHP code base. A simpler and better approach is EditorConfig and fixing code using some code style fixing tools in the future instead. This patch also removes the so called modelines for Vim. Modelines allow Vim editor specifically to set some editor configuration such as syntax highlighting, indentation style and tab width to be set in the first line or the last 5 lines per file basis. Since the php test files have syntax highlighting already set in most editors properly and EditorConfig takes care of the indentation settings, this patch removes these as well for the Vim 6.0 and newer versions. With the removal of local variables for certain editors such as Emacs and Vim, the footer is also probably not needed anymore when creating extensions using ext_skel.php script. Additionally, Vim modelines for setting php syntax and some editor settings has been removed from some *.phpt files. All these are mostly not relevant for phpt files neither work properly in the middle of the file.
* | Remove yearly range from copyright noticeZeev Suraski2019-01-302-2/+2
| |
* | Implement typed propertiesNikita Popov2019-01-111-3/+5
| | | | | | | | | | | | | | | | | | | | RFC: https://wiki.php.net/rfc/typed_properties_v2 This is a squash of PR #3734, which is a squash of PR #3313. Co-authored-by: Bob Weinand <bobwei9@hotmail.com> Co-authored-by: Joe Watkins <krakjoe@php.net> Co-authored-by: Dmitry Stogov <dmitry@zend.com>
* | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-141-1/+1
| |
* | Trim trailing whitespace in testsGabriel Caruso2018-10-1422-82/+82
| |
* | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 unused ext/enchant/tests filesPeter Kokot2018-09-252-2/+0
| | | | | | | | | | | | | | - ext/enchant/tests/hindi_correct.txt - ext/enchant/tests/hindi_incorrect.txt Added via 5956f9a3984249a763ce629532a01073de8109fe but never used.
* | Change some permissions from 755 to 644Peter Kokot2018-08-281-0/+0
| | | | | | | | | | This patch syncs file permissions accross the PHP source code files since these don't need to be executable.
* | Remove unecessaries percent signsGabriel Caruso2018-08-051-2/+2
|/
* Remove unused Git attributes identPeter Kokot2018-07-253-6/+1
| | | | | | | | | | | | | | | The $Id$ keywords were used in Subversion where they can be substituted with filename, last revision number change, last changed date, and last user who changed it. In Git this functionality is different and can be done with Git attribute ident. These need to be defined manually for each file in the .gitattributes file and are afterwards replaced with 40-character hexadecimal blob object name which is based only on the particular file contents. This patch simplifies handling of $Id$ keywords by removing them since they are not used anymore.
* Remove enchant version from the phpinfo outputPeter Kokot2018-06-041-4/+1
| | | | This patch syncs the phpinfo output with other bundled extensions.
* Merge branch 'PHP-7.2'Thomas Punt2018-04-291-1/+1
|\ | | | | | | | | | | * PHP-7.2: Fix potential memory leak in the enchant extension Fix potential memory leak in curl extension
| * Fix potential memory leak in the enchant extensionThomas Punt2018-04-291-1/+1
| |
| * year++Xinchen Hui2018-01-022-2/+2
| |
* | Use bool instead of boolean in protoGabriel Caruso2018-02-041-1/+1
| |
* | year++Xinchen Hui2018-01-022-2/+2
| |
* | Move constants into read-only data segmentDmitry Stogov2017-12-141-1/+1
| |
* | Encapsulate reference-counting primitives.Dmitry Stogov2017-10-271-2/+2
| | | | | | | | | | | | Prohibit direct update of GC_REFCOUNT(), GC_SET_REFCOUNT(), GC_ADDREF() and GC_DELREF() shoukf be instead. Added mactros to validate reference-counting (disabled for now). These macros are going to be used to eliminate race-condintions during reference-counting on data shared between threads.
* | Merge branch 'PHP-7.2'Christoph M. Becker2017-10-152-0/+25
|\ \ | |/ | | | | | | * PHP-7.2: Fixed bug #53070 (enchant_broker_get_path crashes if no path is set)
| * Merge branch 'PHP-7.0' into PHP-7.1Christoph M. Becker2017-10-152-0/+25
| |\ | | | | | | | | | | | | * PHP-7.0: Fixed bug #53070 (enchant_broker_get_path crashes if no path is set)
| | * Fixed bug #53070 (enchant_broker_get_path crashes if no path is set)Jelle van der Waa2017-10-152-0/+25
| | | | | | | | | | | | | | | enchant_broker_get_dict_path segfaults when the dict path is not setup, instead of segfaulting return false instead.
* | | Merge branch 'PHP-7.2'Christoph M. Becker2017-10-152-2/+1
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fixed bug #75365 (Enchant still reports version 1.1.0)
| * | Merge branch 'PHP-7.0' into PHP-7.1Christoph M. Becker2017-10-152-2/+1
| |\ \ | | |/ | | | | | | | | | * PHP-7.0: Fixed bug #75365 (Enchant still reports version 1.1.0)
| | * Fixed bug #75365 (Enchant still reports version 1.1.0)Christoph M. Becker2017-10-152-2/+1
| | | | | | | | | | | | | | | | | | Since Enchant is bundled, we make `PHP_ENCHANT_VERSION` an alias of `PHP_VERSION` and also drop the rather meaningless revision hash from the PHP info.
| | * Update copyright headers to 2017Sammy Kaye Powers2017-01-042-2/+2
| | |
| * | Update copyright headers to 2017Sammy Kaye Powers2017-01-042-2/+2
| | |
* | | Remove enchant PHP examplePeter Kokot2017-10-051-25/+0
| | |
* | | Get rid of all these old package[2].xml files, most of these had no had a ↵Kalle Sommer Nielsen2017-08-171-162/+0
| | | | | | | | | | | | | | | | | | release since PHP4, or any release at all in close to 10 years, some even did not have a package registered at pecl OCI, PDO_OCI and zip are left as they are actively developed and released there
* | | Skip these enchant tests if no dicts or providers are installedKalle Sommer Nielsen2017-07-253-6/+59
| | |
* | | Update copyright headers to 2017Sammy Kaye Powers2017-01-022-2/+2
|/ /
* | Remove version checksNikita Popov2016-01-301-4/+0
|/ | | | | | | | | | | PHP_VERSION_ID PHP_API_VERSION ZEND_MODULE_API_NO PHP_MAJOR_VERSION, PHP_MINOR_VERSION ZEND_ENGINE_2 I've left litespeed alone, as it seems to genuinely maintain support for many PHP versions.
* Update header to PHP Version 7Lior Kaplan2016-01-011-1/+1
|
* Merge branch 'PHP-5.6' into PHP-7.0Lior Kaplan2016-01-012-2/+2
|\ | | | | | | | | * PHP-5.6: Happy new year (Update copyright to 2016)
| * Happy new year (Update copyright to 2016)Lior Kaplan2016-01-012-2/+2
| |
* | Merge branch 'pull-request/1471'Christoph M. Becker2015-08-191-0/+59
|\ \ | | | | | | | | | | | | * pull-request/1471: add test for php_enchant_broker_free()
| * | add test for php_enchant_broker_free()marcosptf2015-08-191-0/+59
| | |
View Lorry Controller Status