Von professionellen Übersetzern, Unternehmen, Websites und kostenlos verfügbaren Übersetzungsdatenbanken.
add a launch annotation (to a target of arbitrary file type).
add a launch annotation (to a target of arbitrary file type).
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
dba is binary safe and does not have any arbitrary limits. it inherits all limits set by the underlying database implementation.
the functions dba_open() and dba_popen() return a handle to the specified database file to access which is used by all other dba-function calls.
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
note that if you are going to allow data coming from user input to be passed to this function, then you should be using escapeshellcmd() to make sure that users cannot trick the system into executing arbitrary commands.
if you are going to allow data coming from user input to be passed to this function, then you should be using escapeshellarg() or escapeshellcmd() to make sure that users cannot trick the system into executing arbitrary commands.
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
note, that if you are going to allow data coming from user input to be passed to this function, then you should be using the escapeshellcmd() function to make sure that users cannot trick the system into executing arbitrary commands.
if you are going to allow data coming from user input to be passed to this function, then you should be using escapeshellarg() or escapeshellcmd() to make sure that users cannot trick the system into executing arbitrary commands.
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
따라서 실수 결과값에 대해서는 마지막 자리의 값을 믿지 말도록 하고, 실수끼리는 = 등의 '같다' 비교를 하지 않도록 하자. 만약 여러분이 좀더 높은 정밀도를 필요로 한다면 arbitrary precision math functions 이나 gmp 에 있는 함수들을 사용하기 바란다.
for values of other types, the conversion is the same as if the value would have been converted to integer and then to float.
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
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.
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.
Letzte Aktualisierung: 2011-10-24
Nutzungshäufigkeit: 1
Qualität:
Warnung: Enthält unsichtbare HTML-Formatierung