New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Family mb_*-functions mutators #654
Comments
I'd prefer to have a map which holds |
Great idea. As I understand, both your implementation suggestions mean we will have 1 mutator class that mutates N functions, right? In this case, we need |
Funny I already have this mutator stashed on mine laptop ;-) Will create PR when I get back to home |
* #654 mbstring mutator * #654 mbstring mutator configuration * #654 fix code analysis issues * #654 update json scheme for MBString mutator * #654 fix spaceing * #654 remove mutants * #654 drop ereg functions in favoure of preg functions * #654 fix styles * #654 drop support fro mb_ereg* functions * #654 mutate mb_convert_case with integer mode * #654 remove functions that cannot be easily mapped * #654 rm mb_split from json schema * #654 rm mb_strrichr from json schema * #654 code style fixes * #654 simplify MBString mutator * #654 remove getFunctionName fx * #654 add tests cases for capitalization * #654 add test for calling functions via variable
As the PR is merged do we closes the issue ? BTW thanks for great feedback during review. |
Sure, should be closed BTW, if the Thanks for adding this feature, nice contribution! |
It is common to see people use multibyte string functions (like
mb_strlen
) instead of their common analogs (likestrlen
), while not writing any tests exploiting multibyte functionality.In this situations mutators as simple as below could be of use:
And similar mutators for functions like
mb_substr
, and others.(This mutator could simply check if a function call starts with
mb_
, and then replace the function name with a prefix-less function if it exists, though this may not be the best approach.)The text was updated successfully, but these errors were encountered: