OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
defs:POSSIBLE
(Results
1 - 4
of
4
) sorted by null
/external/chromium_org/third_party/libphonenumber/src/phonenumbers/
phonenumbermatcher.h
55
// Phone numbers accepted are
possible
, but not necessarily valid.
56
POSSIBLE
,
57
// Phone numbers accepted are
possible
and valid.
59
// Phone numbers accepted are valid and are grouped in a
possible
way for
/external/chromium_org/v8/src/
effects.h
20
// or '
possible
', if it was optional. The difference is relevant when composing
25
// effect cancels out any previous effect upon sequencing. A
possible
effect
27
// composition always merges bounds. It yields a
possible
effect if at least
28
// one was only
possible
.
30
enum Modality {
POSSIBLE
, DEFINITE };
40
return Effect(Bounds::Unbounded(zone),
POSSIBLE
);
57
e1.modality ==
POSSIBLE
?
POSSIBLE
: e2.modality);
152
effect.modality = Effect::
POSSIBLE
;
/external/libphonenumber/java/src/com/android/i18n/phonenumbers/
PhoneNumberUtil.java
294
// Regexp of all
possible
ways to write extensions, for use when parsing. This will be run as a
303
// allow a "comma" as a
possible
extension indicator. When matching, this is hardly ever used to
427
*
Possible
outcomes when testing if a PhoneNumber is
possible
.
443
*
possible
}, but not necessarily {@linkplain PhoneNumberUtil#isValidNumber(PhoneNumber) valid}.
445
POSSIBLE
{
453
*
possible
} and {@linkplain PhoneNumberUtil#isValidNumber(PhoneNumber) valid}. Numbers written
469
* are grouped in a
possible
way for this locale. For example, a US number written as
[
all
...]
/packages/apps/ContactsCommon/libs/
libphonenumber-6.2.jar
Completed in 1811 milliseconds