1.0.3 2014-09-19 19:13 UTC


Build Status Scrutinizer Code Quality

This project aims to provide a dead simple component for php to support wildcards. Wildcards are * (zero or more character) and ? (exactly one character). The component is not tied to filenames. You can use it also for namespaces, urls and other strings.

Why can't you just provide a simple function for this?

Because of effectivity. When you create an instance of the Pattern-class, you also "compile" the pattern. This means that I try to find the optimal test method for your later input. So if you run the same pattern more often in the same run, you could benefit from that optimization. If not, the Interface should still be simple enough to make you happy. If not, go wrap a function around it.

Why not just use regular expressions?

Because there is no reason to use regular expressions for the most common figures:

string* means "starts with".
*string means "ends with".

So even if I use regular expressions to cover complex patterns, it is too pointless to use regular expressions for one of these. Internally I use substr() instead. If you like to provide more speedups for such simple patterns, feel free to push me some.


use Kir\StringUtils\Matching\Wildcards\Pattern;

echo (new Pattern('test.*'))->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('test.*')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('*.txt')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('*.*')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('test*txt')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('test?txt')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('t*.???')->match('test.txt') ? "is matching\n" : "is not matching\n";
echo Pattern::create('t*?.txt')->match('test8.txt') ? "is matching\n" : "is not matching\n";


"require": [
	"rkr/wildcards": "1.*"