|
mb_strlen
Get string length
(PHP 4 >= 4.0.6, PHP 5)
Code Examples / Notes » mb_strlenmotin
Thank you Peter Albertsson for presenting that! After spending more than eight hours tracking down two specific bugs in my mbstring-func_overloaded environment I have learned a very important lesson: Many developers rely on strlen to give the amount of bytes in a string. While mb-overloading has very many advantages, the most hard-spotted pitfall must be this issue. Two examples (from the two bugs found earlier): 1. Writing a string to a file: <?php $str = "string with utf-8 chars åèä - doo-bee doo-bee dooh"; $fp = fopen($this->_file, "wb"); if ($fp) { $len = strlen($str); fwrite($fp, $str, $len); } ?> PS This is found i the PEAR::Cache_Lite package (Lite.php) - Reported 2. Iterating through a string's characters: <?php $str = "string with utf-8 chars åèö - doo-bee doo-bee dooh"; $newStr = ""; for ($i = 0; $i < strlen($str); $i++) { $newStr .= $str[$i]; } ?> Both of these situations will fail to save / store the last characters in $str. This can be very hard to spot and can be especially fatal for say serialized strings, xml etc. So, try to avoid these situations to support overloaded environments, and remeber Peter Albertssons remark if you find problems under such an environment. drake127
Speed of mb_strlen varies a lot according to specified character set. If you need length of string in bytes (strlen cannot be trusted anymore because of mbstring.func_overload) you should use <?php mb_strlen($string, '8bit'); ?>. It's the fastest way (still a way slower than strlen, though) to determine byte length of string. Other single byte character sets (ASCII, ISO-8859-1, ...) are several times slower than 8bit. koala
Just did a little benchmarking (1.000.000 times with lorem ipsum text) on the mbs functions especially mb_strtolower and mb_strtoupper are really slow (up to 100 times slower compared to normal functions). Other functions are alike-ish, but sometimes up to 5 times slower. just be cautious when using mb_ functions in high frequented scripts. # test runs: 1000000 # benchmarking strlen vs. mb_strlen # normal strlen: 3.6795361042023 ms, average: 3.6795361042023E-6 ms # mb_strlen: 5.5934538841248 ms, average: 5.5934538841248E-6 ms ok 1 - mb_strlen is slower than strlen # mb_strlen is 1.52 slower than strlen # # # benchmarking strpos vs. mb_strpos # normal strpos: 5.5523281097412 ms, average: 5.5523281097412E-6 ms # mb_strlen: 31.180974960327 ms, average: 3.1180974960327E-5 ms ok 2 - mb_strlen is slower than strlen # mb_strpos is 5.62 slower than strpos # # # benchmarking substr vs. mb_substr # normal substr: 3.4437320232391 ms, average: 3.4437320232391E-6 ms # mb_strlen: 3.5374181270599 ms, average: 3.5374181270599E-6 ms ok 3 - mb_strlen is slower than strlen # mb_substr is 1.03 slower than substr # # # benchmarking strtolower vs. mb_strtolower # normal strtolower: 4.446839094162 ms, average: 4.446839094162E-6 ms # mb_strlen: 193.44901108742 ms, average: 0.00019344901108742 ms ok 4 - mb_strlen is slower than strlen # mb_strtolower is 43.5 slower than strtolower # # # benchmarking strtoupper vs. mb_strtoupper # normal strtoupper: 3.0210740566254 ms, average: 3.0210740566254E-6 ms # mb_strlen: 340.71775603294 ms, average: 0.00034071775603294 ms ok 5 - mb_strlen is slower than strlen # mb_strtoupper is 112.78 slower than strtoupper peter albertsson
If you wish to find the byte length of a multi-byte string when you are using mbstring.func_overload 2 and UTF-8 strings, then you can use the following: mb_strlen($utf8_string, 'latin1'); filatei
I have been working with some funny html characters lately and due to the nightmare in manipulating them between mysql and php, I got the database column set to utf8, then store characters with html enity "ọ" as á» in the database and set the encoding on php as "utf8". This is where mb_strlen became more useful than strlen. While strlen('á»') gives result as 3, mb_strlen('á»','UTF-8') gives 1 as expected. But left(column1,1) in mysql still gives wrong char for a multibyte string. In the example above, I had to do left(column1,3) to get the correct string from mysql. I am now about to investigate multibyte manipulation in mysql. |
Change Languagemb_check_encoding mb_convert_case mb_convert_encoding mb_convert_kana mb_convert_variables mb_decode_mimeheader mb_decode_numericentity mb_detect_encoding mb_detect_order mb_encode_mimeheader mb_encode_numericentity mb_ereg_match mb_ereg_replace mb_ereg_search_getpos mb_ereg_search_getregs mb_ereg_search_init mb_ereg_search_pos mb_ereg_search_regs mb_ereg_search_setpos mb_ereg_search mb_ereg mb_eregi_replace mb_eregi mb_get_info mb_http_input mb_http_output mb_internal_encoding mb_language mb_output_handler mb_parse_str mb_preferred_mime_name mb_regex_encoding mb_regex_set_options mb_send_mail mb_split mb_strcut mb_strimwidth mb_stripos mb_stristr mb_strlen mb_strpos mb_strrchr mb_strrichr mb_strripos mb_strrpos mb_strstr mb_strtolower mb_strtoupper mb_strwidth mb_substitute_character mb_substr_count mb_substr |