The behaviour of mb_ereg_match to imply a ^ at the beginning of the pattern stands in stark contrast to the behaviour of mb_ereg where ^ is NOT implied.
Switching between those two routines (because the need to extract a subpattern changes) requires careful consideration when to compensate for this surprising inconsistence.
mb_ereg_match
(PHP 4 >= 4.2.0, PHP 5, PHP 7, PHP 8)
mb_ereg_match — Compararción de expresiones regulares para strings multibyte
Descripción
Una compararción de expresiones regulares para strings multibyte.
Valores devueltos
Devuelve true si
string coincide con la expresión regular
pattern, false si no.
Notas
Nota:
La codificación interna o la codificación especificada por mb_regex_encoding() será usada en esta función.
Ver también
- mb_regex_encoding() - Establecer/obtener la codificación de caracteres para expresiones regulares multibyte
- mb_ereg() - Comparación de expresiones regulares con soporte multibyte
add a note
User Contributed Notes 3 notes
Anonymous ¶
8 years ago
Anonymous ¶
16 years ago
Note that this function matches a string from the beginning only (though not necessarily till the end):
<?php
$test = mb_ereg_match("a", "some apples"); // returns false
$test = mb_ereg_match("a", "a kiwi"); // returns true
?>
If you want to check for a match anywhere in the string, use the wild-card & repeat operators .*
<?php
$test = mb_ereg_match(".*a", "some apples"); // returns true
?>
webdesign at innato dot nl ¶
5 years ago
It took me a while to discover that you must escape characters like parentheses (), square brackets [] and ^ (and maybe more) if you want to match these as a literal. Otherwise you may get some erratic outcome.
In summary, using a match anywhere in the string as an example:
<?php
$needle = "[";
$haystack = "some_array[]";
$test= mb_ereg_match(".*".$needle, $haystack); // returns false and a php warning
$test= mb_ereg_match('.*'.preg_quote($needle), $haystack); // returns true
?>
