Add a test case for Github issue 27
Add ‘yield’ to the list of PHP keywords

This keyword is part of PHP 5.5’s new generator mechanism, described
here with examples:

    https://wiki.php.net/rfc/generators
Add the new ‘PASSWORD_*’ values to the list of PHP constants

These are new as of PHP 5.5.  See the RFC at

    https://wiki.php.net/rfc/password_hash

for more details.
Make the php-keywords list easier to read and edit

This patch breaks up the strings in the php-keywords list so that one
string appears per line, in alphabetical order.  This makes it a
little easier to see if at a glance if anything is missing, and also
decreases the chance to two patches modifying php-keywords would ever
conflict by changing the same line.

There are no logic changes in this patch.  It modifies whitespace and
layout only.
Treat ‘array’ and ‘list’ as PHP keywords

Strictly speaking neither ‘array()’ or ‘list()’ are functions.  The
PHP manual describes them as language constructs.  Since we already
treat ‘die()’ like a language construct we should be consistent and do
the same with these two.  Also, being able to write code in PHP 5.5
such as

    foreach ($users as list($firstName, $lastName)) {
        echo "First name: $firstName, last name: $lastName. ";
    }

makes it more obvious that ‘list()’ is not a function.  By treating
these two function-ish constructs like keywords we help emphasize the
special treatment they receive in PHP, which may help when users try
to do something like use ‘array()’ as a callback function and wonder
why it fails.
Add ‘empty’ and ‘isset’ to the list of PHP keywords

These are language constructs and not functions, even though they
appear to be so.  We add them to the list of keywords for
the sake of consistency with other entries.
Remove ‘return new’ from the list of PHP keywords

Both of the individual keywords are properly dealt with elsewhere.  We
do not need a single entry in php-keywords handling both together.
Treat ‘callable’ as a valid type, e.g. for type-hints in functions
Add ‘unset’ as a PHP keyword

Commit 899cdeec added ‘isset’ to this list so it only makes sense to
add ‘unset’ as well.  Why have one but not the other?
Move the settings for PEAR coding into its own function

This is the first step towards making it possible to select a variety
of coding styles for popular projects (e.g. Drupal, Wordpress) by
using ‘M-x customize’ to select the style.  This patch makes no logic
changes to the code; it only moves some things around.

Github-issue: 33

Signed-off-by: Eric James Michael Ritz <lobbyjones@gmail.com>
Add a function for enabling Drupal coding settings

These are formatting and indentation settings which are preferable
when working with the Drupal source code.  This code comes from the

    https://github.com/jrbeeman/drupal-mode

project repository.

Github-issue: 33

Signed-off-by: Eric James Michael Ritz <lobbyjones@gmail.com>
Mention in the README that the mode is conscious of PHP 5.5 features
Fontify function calls qualified with one namespace

This patch causes proper highlighting for code like

    Foo\bar();

but still does not work properly for longer namespaces, e.g. those
which use more than one backslash.

Github-issue: 26
Add a function to enable a coding style suitable for Wordpress

Github-issue: 33

Signed-off-by: Eric James Michael Ritz <lobbyjones@gmail.com>
Document how to change default coding styles in the README
Merge branch 'php5.5-keywords'

* php5.5-keywords:
  Mention in the README that the mode is conscious of PHP 5.5 features
  Add ‘unset’ as a PHP keyword
  Treat ‘callable’ as a valid type, e.g. for type-hints in functions
  Remove ‘return new’ from the list of PHP keywords
  Add ‘empty’ and ‘isset’ to the list of PHP keywords
  Treat ‘array’ and ‘list’ as PHP keywords
  Make the php-keywords list easier to read and edit
  Add the new ‘PASSWORD_*’ values to the list of PHP constants
  Add ‘yield’ to the list of PHP keywords
Merge branch 'issue-27'

* issue-27:
  Add a test case for Github issue 27
Merge branch 'issue-26'

* issue-26:
  Fontify function calls qualified with one namespace
Merge branch 'customize-coding-styles'

* customize-coding-styles:
  Document how to change default coding styles in the README
  Add a function to enable a coding style suitable for Wordpress
  Add a function for enabling Drupal coding settings
  Move the settings for PEAR coding into its own function
Update the changelog and module meta-info for version 1.9