PHP Regular expressions made easy

I was wondering if support for 5.3 to 5.5 would be an option, if the slow func_get_args would be just a different implementation of the single method, provided in another class.

A (new) abstract class would use: protected function range(array $args) The existing class would just call parent::range($args) A new class for older php would use parent::range(func_get_args())

That would allow older versions to work without negatively impacting the performance of newer versions of php and the change would not break current code. Tests would need to be expanded to check that both range-implementations work the same if covering the single new line is desired.

If desired I'll write the required code, I'd like to have a 5.3 compatible version in any case.

I have added the possibility to define the expression via a business readable language.

$definition = 'start, then "http", maybe "s", then "://", maybe "www.", anything but " ", end';
$regex = new VerbalExpressionsScenario($definition);

I have also updated the README with a list of the VerbalExpressions methods.

I've swapped out the unit test for a travis test :D

The readme.md image refers to your own repo, so you'll need to enable it on travis-ci.org

It works though (see mine):

In order to install this lib with Composer I have re-structured the project. Besides I added PHPUnit (installed by Composer) and wrote the very first testcase (yet to be extended) as showcase.

If this PR is accepted I will add more testcases.

In addition I fixed the return value of VerbalExpressions. Originally int was returned but it should be bool.

I'm wondering if the library is by now stable enough to be given a tag - likely 1.0.0 - so it's less risky to depend on this library. Having a version just makes it way easier to tie down a specific api.

Hello,

I propose these changes to increase consistency:

• Always use "@access public" if a method is public
• Always start the additional description text of a method with an upper case letter

Moved squizlabs/php_codesniffer to require-dev, since there is zero need for it in a production enviroment.

Adjusted the examples in Example.php and the Readme.md to comply with PSR2, since the whole project has defined it as it's desired standard.

At first I wasn't be able to run tests, so I did some changes in that field, accordingly to best practices. I also switched from user_func_args() to variadic args, which is several times faster as there is no function call overhead. I have described all my actions in commit log.

I've noticed that JSVerbalExpressions & PHPVerbalExpressions don't produce the same output for the same input; Which of the VerbalExpressions projects is considered the "master" to test against?

example: input: regex->startOfLine()->range(0, 9, 'a', 'z', 'A', 'Z')->multiple('')

$js = '/^[0-9a-zA-Z](?:)*/gm';

$php = '/^[0-9a-zA-Z]+/m';

(variables edited to clarify language)

| Q | A | | --- | --- | | Bug fix? | no | | Enhancement? | yes | | New feature? | no | | BC breaks? | no | | Deprecations? | no | | Tests pass? | yes |

Hi, it would be important to describe in composer.json which PHP versions is minimum for using this package (as described on http://getcomposer.org/doc/02-libraries.md#platform-packages)

Example:

{
    // ...
    "require": {
        // ...
        "php": ">=5.2"
    }
}

Hello,

It seems it's not possible to do something like:

$regex->anythingBut('0-9')

since the sanitize method add systematically a "\" behind the "-" which break the regex range expression. That giving us:

(?:[^0\-9]*) instead of (?:[^0-9]*)

Thanks a lot, Aurélien