Remove deprecated compile

[SignpostMarv]

While not strictly necessary, this builds upon #136 in order to verify the refactoring has not affected functionality.

While we don't have #31 closed yet, I'm going to assume that the refactored toRegExp & test methods have the same or lower performance impact as calling RegExp.compile() on VerEx().add().

It will however break anything that expects VerEx() to be an instanceof RegExp.

[softwarespot]

Was there a reason you changed setting the prototype all at one to individually?

VerbalExpression.prototype = {
    anything: function anything() ...
}

// to

VerbalExpression.prototype.anything = function anything() ...

[SignpostMarv]

We're using airbnb/legacy for linting, the airbnb style guide on constructors suggests assigning to the prototype object instead of defining it.

[softwarespot]

Ah fair point, kind of missed that part in the style guide as I write in ES2015 these days and not ES5. Just a shame eslint doesn't warn about this.

[jehna]

So this makes the VerbalExpressions behave more like a proper Builder.

I can see this is technically a better approach, since the current implementation requires a heavy injecting method to run each time we create a new object.

However, I'd see we could easily keep this library backwards-compatible by just implementing the native RegExp object's methods so they could be called straight from the VebalExpression object (as you've now done with .test() method). What do you think?

In addition, the README.md file should be changed not to state that this is a native RegExp method.

[SignpostMarv]

we've got toString, toSource seems to be firefox-only, compile is deprecated (thus removed), so I guess we just need .exec() ?

If we're taking the backwards compatibility approach of making the RegExp methods available, should we have a plan for required level of support for methods introduced/removed in future standards?

[mihai-vlc]

Is this still relevant or can we close it ?