| commit | ba09144ce5210c1ae5a07389d4de5085938601c3 | |
| author | Slava Zanko <slavazanko@gmail.com> | |
| Fri, 8 Jul 2011 16:39:35 +0000 (8 19:39 +0300) | ||
| committer | Slava Zanko <slavazanko@gmail.com> | |
| Fri, 8 Jul 2011 16:39:35 +0000 (8 19:39 +0300) | ||
| tree | 4810218cc10958b290d1834b872540067621e0c8 | treesnapshot (tar.gz zip) |
| parent | bb12a1296f3712e8828c6ed89936e991d35259ee | commitdiff |
| parent | e1edfd7c93d62c89645f1500255bb852a65fa416 | commitdiff |
Merge branch '1882_esc_seq_in_replace_field'
* 1882_esc_seq_in_replace_field:
Remove replace_prepare_t type and use defined constants for use just one type (int) in functions
Despite of the fact that algorithm now ignores the absence of closing curly brace '}' (which probably isn't 100% correct), this should be checked in tests for replace_handle_esc_seq function, not process_escape_sequence - it is the replace_handle_esq_seq who decides whether it is an escape sequence or not.
added tests for mc_search_regex__replace_handle_esc_seq() function
str_isutf8() function now returns gboolean value
Ticket #1882: PCRE search: escape sequence support in replacements, UTF8 support (just a flag for libPCRE)
* 1882_esc_seq_in_replace_field:
Remove replace_prepare_t type and use defined constants for use just one type (int) in functions
Despite of the fact that algorithm now ignores the absence of closing curly brace '}' (which probably isn't 100% correct), this should be checked in tests for replace_handle_esc_seq function, not process_escape_sequence - it is the replace_handle_esq_seq who decides whether it is an escape sequence or not.
added tests for mc_search_regex__replace_handle_esc_seq() function
str_isutf8() function now returns gboolean value
Ticket #1882: PCRE search: escape sequence support in replacements, UTF8 support (just a flag for libPCRE)