Você procurou por: allowing (Coreano - Inglês)

Tradução automática

Tentando aprender a traduzir a partir dos exemplos de tradução humana.

Korean

English

Informações

Korean

allowing

English

 

De: Tradução automática
Sugerir uma tradução melhor
Qualidade:

Contribuições humanas

A partir de tradutores profissionais, empresas, páginas da web e repositórios de traduções disponíveis gratuitamente

Adicionar uma tradução

Coreano

Inglês

Informações

Coreano

tick this box add caption text to the image. the caption text will appear below the image, allowing you to introduce or explain the image.

Inglês

check this box add caption text to the image. the caption text will appear below the image, allowing you to introduce or explain the image.

Última atualização: 2011-10-23
Frequência de uso: 1
Qualidade:

Coreano

consider the problem of matching a string in parentheses, allowing for unlimited nested parentheses. without the use of recursion, the best that can be done is to use a pattern that matches up to some fixed depth of nesting. it is not possible to handle an arbitrary nesting depth. perl 5.6 has provided an experimental facility that allows regular expressions to recurse (amongst other things). the special item (?r) is provided for the specific case of recursion. this pcre pattern solves the parentheses problem (assume the pcre_extended option is set so that white space is ignored): \( ((? [^()]+) _bar_ (?r) )*\) first it matches an opening parenthesis. then it matches any number of substrings which can either be a sequence of non- parentheses, or a recursive match of the pattern itself (i.e. a correctly parenthesized substring). finally there is a closing parenthesis. this particular example pattern contains nested unlimited repeats, and so the use of a once-only subpattern for matching strings of non-parentheses is important when applying the pattern to strings that do not match. for example, when it is applied to (aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa() it yields "no match" quickly. however, if a once-only subpattern is not used, the match runs for a very long time indeed because there are so many different ways the + and * repeats can carve up the subject, and all have to be tested before failure can be reported. the values set for any capturing subpatterns are those from the outermost level of the recursion at which the subpattern value is set. if the pattern above is matched against (ab(cd)ef) the value for the capturing parentheses is "ef", which is the last value taken on at the top level. if additional parentheses are added, giving \( (((? [^()]+) _bar_ (?r) )*)\) ^ ^ ^ ^ then the string they capture is "ab(cd)ef", the contents of the top level parentheses. if there are more than 15 capturing parentheses in a pattern, pcre has to obtain extra memory to store data during a recursion, which it does by using pcre_malloc, freeing it via pcre_free afterwards. if no memory can be obtained, it saves data for the first 15 capturing parentheses only, as there is no way to give an out-of-memory error from within a recursion.

Inglês

an optimization catches some of the more simple cases such as (a+)*ban optimization catches some of the more simple cases such as (a+ )*b where a literal character follows.

Última atualização: 2011-10-24
Frequência de uso: 1
Qualidade:

Aviso: contém formatação HTML invisível

Consiga uma tradução melhor através
7,746,539,261 de colaborações humanas

Usuários estão solicitando auxílio neste momento:



Utilizamos cookies para aprimorar sua experiência. Se avançar no acesso a este site, você estará concordando com o uso dos nossos cookies. Saiba mais. OK