Results for described translation from Korean to English

Korean

Translate

described

Translate

English

Translate
Translate

Instantly translate texts, documents and voice with Lara

Translate now

Human contributions

From professional translators, enterprises, web pages and freely available translation repositories.

Add a translation

Korean

English

Info

Korean

the differences described here are with respect to perl 5.005.

English

capturing subpatterns that occur inside negative looka - head assertions are counted, but their entries in the offsets vector are never set.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

this is the notation's name, as per the notation format described above.

English

system identifier of the external notation declaration.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

cainfo should be an array of trusted ca files/dirs as described in certificate verification.

English

can the certificate be used for the client side of an ssl connection?

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

dba_replace() replaces or inserts the entry described with key and value into the database specified by handle.

English

dba_replace() replaces or inserts the entry described with key and value into the database specified by handle.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

display array values as a formatted string according to format (which is described in the documentation for sprintf()).

English

display array values as a formatted string according to format (which is described in the documentation for sprintf()).

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

zend is built using certain conventions; to avoid breaking its standards, you should follow the rules described in the following sections.

English

zend is built using certain conventions; to avoid breaking its standards, you should follow the rules described in the following sections.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

mb_regex_set_options() sets the default options described by options for multibyte regex functions.

English

mb_regex_set_options() sets the default options described by options for multibyte regex functions.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

the socket functions described here are part of an extension to php which must be enabled at compile time by giving the --enable-sockets option to configure.

English

use this extension at your own risk.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

dba_insert() inserts the entry described with key and value into the database specified by handle. it fails, if an entry with the same key already exists.

English

dba_insert() inserts the entry described with key and value into the database specified by handle.

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Korean

an assertion is a test on the characters following or preceding the current matching point that does not actually consume any characters. the simple assertions coded as \b, \b, \a, \z, \z, ^ and $are described above. more complicated assertions are coded as subpatterns. there are two kinds: those that look ahead of the current position in the subject string, and those that look behind it. an assertion subpattern is matched in the normal way, except that it does not cause the current matching position to be changed. lookahead assertions start with (?= for positive assertions and (?! for negative assertions. for example, \w+(?=;) matches a word followed by a semicolon, but does not include the semicolon in the match, and foo(?!bar) matches any occurrence of "foo" that is not followed by "bar". note that the apparently similar pattern (?!foo)bar does not find an occurrence of "bar" that is preceded by something other than "foo"; it finds any occurrence of "bar" whatsoever, because the assertion (?!foo) is always true when the next three characters are "bar". a lookbehind assertion is needed to achieve this effect. lookbehind assertions start with (? = for positive assertions and (?! for negative assertions. for example, (? !foo)bar does find an occurrence of "bar" that is not preceded by "foo". the contents of a lookbehind assertion are restricted such that all the strings it matches must have a fixed length. however, if there are several alternatives, they do not all have to have the same fixed length. thus (? =bullock_bar_donkey) is permitted, but (? !dogs?_bar_cats?) causes an error at compile time. branches that match different length strings are permitted only at the top level of a lookbehind assertion. this is an extension compared with perl 5.005, which requires all branches to match the same length of string. an assertion such as (? =ab(c_bar_de)) is not permitted, because its single top-level branch can match two different lengths, but it is acceptable if rewritten to use two top-level branches: (? =abc_bar_abde) the implementation of lookbehind assertions is, for each alternative, to temporarily move the current position back by the fixed width and then try to match. if there are insufficient characters before the current position, the match is deemed to fail. lookbehinds in conjunction with once-only subpatterns can be particularly useful for matching at the ends of strings; an example is given at the end of the section on once-only subpatterns. several assertions (of any sort) may occur in succession. for example, (? =\d{3})(? !999)foo matches "foo" preceded by three digits that are not "999". notice that each of the assertions is applied independently at the same point in the subject string. first there is a check that the previous three characters are all digits, then there is a check that the same three characters are not "999". this pattern does not match "foo" preceded by six characters, the first of which are digits and the last three of which are not "999". for example, it doesn't match "123abcfoo". a pattern to do that is (? =\d{3}...)(? !999)foo this time the first assertion looks at the preceding six characters, checking that the first three are digits, and then the second assertion checks that the preceding three characters are not "999". assertions can be nested in any combination. for example, (? =(? !foo)bar)baz matches an occurrence of "baz" that is preceded by "bar" which in turn is not preceded by "foo", while (? =\d{3}(?!999)...)foo is another pattern which matches "foo" preceded by three digits and any three characters that are not "999". assertion subpatterns are not capturing subpatterns, and may not be repeated, because it makes no sense to assert the same thing several times. if any kind of assertion contains capturing subpatterns within it, these are counted for the purposes of numbering the capturing subpatterns in the whole pattern. however, substring capturing is carried out only for positive assertions, because it does not make sense for negative assertions. assertions count towards the maximum of 200 parenthesized subpatterns.

English

it is more efficient to use a character class like [aeiou] than a set of alternatives such as (a_bar_e_bar_i_bar_o_bar_u).

Last Update: 2011-10-24
Usage Frequency: 1
Quality:

Warning: Contains invisible HTML formatting

Get a better translation with
8,897,425,488 human contributions

Users are now asking for help:



We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Learn more. OK