HomeSort by relevance Sort by last modified time
    Searched full:braces (Results 76 - 100 of 640) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/libcxxabi/lib/
buildit 33 -Wmissing-braces -Wshorten-64-to-32 -Wsign-compare \
  /external/libgdx/backends/gdx-backends-gwt/src/com/badlogic/gdx/backends/gwt/emu/com/badlogic/gdx/utils/
TextFormatter.java 83 if (placeholder >= 0) throw new IllegalArgumentException("Unmatched braces in the pattern.");
  /external/llvm/lib/Support/
regerror.c 67 { REG_EBRACE, "REG_EBRACE", "braces not balanced" },
  /external/lz4/examples/
blockStreaming_ringBuffer.c 13 # pragma GCC diagnostic ignored "-Wmissing-braces" /* GCC bug 53119 : doesn't accept { 0 } as initializer (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119) */
  /external/webrtc/third_party/winsdk_samples/
winsdk_samples.gyp 101 '-Wno-missing-braces',
  /external/webrtc/webrtc/base/
base_tests.gyp 143 '-Wno-missing-braces',
  /libcore/luni/src/main/java/javax/xml/transform/
Transformer.java 105 * enclosed in curly braces ({}), followed by the local name. If the
116 * namespace URI in curly braces ({}).
197 * URI enclosed in curly braces ({}), followed by the local name. If the
261 * enclosed in curly braces ({}), followed by the local name. If the
  /ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/lib/
buildit 33 -Wmissing-braces -Wshorten-64-to-32 -Wsign-compare \
  /ndk/sources/host-tools/ndk-stack/regex/
regerror.c 62 { REG_EBRACE, "REG_EBRACE", "braces not balanced" },
  /toolchain/binutils/binutils-2.25/config/
proginstall.m4 87 # Use test -z because SunOS4 sh mishandles braces in ${var-val}.
  /external/guava/guava/src/com/google/common/base/
Verify.java 112 * braces. Unmatched placeholders will be left as-is.
146 * braces. Unmatched placeholders will be left as-is.
Preconditions.java 134 * in square braces. Unmatched placeholders will be left as-is.
186 * in square braces. Unmatched placeholders will be left as-is.
239 * in square braces. Unmatched placeholders will be left as-is.
402 * square braces.
427 // if we run out of placeholders, append the extra args in square braces
  /art/cmdline/
cmdline_parser_test.cc 314 XGcOption option_all_true{}; // NOLINT [readability/braces] [4]
331 XGcOption option_all_false{}; // NOLINT [readability/braces] [4]
346 XGcOption option_all_default{}; // NOLINT [readability/braces] [4]
612 EXPECT_KEY_VALUE(map, M::Help, Unit{}); // NOLINT [whitespace/braces] [5]
615 EXPECT_KEY_VALUE(map, M::MethodTrace, Unit{}); // NOLINT [whitespace/braces] [5]
  /external/mdnsresponder/mDNSPosix/
Identify.c 20 * but for the sake of brevity here I will say just this: Curly braces are not syntactially
24 * Indenting curly braces at the same level as the "if" implies that curly braces are
  /ndk/sources/host-tools/make-3.81/
expand.c 262 /* Is there a variable reference inside the parens or braces?
273 Count parens or braces until it is matched. */
283 or braces, so we go to the simple case of a variable name
  /system/bt/doc/
style_guide.md 307 // Open curly braces are never on a line by themselves.
309 // Conditional statements with only one child statement should elide braces.
317 // braces on both branches.
  /art/compiler/utils/arm/
assembler_arm32_test.cc 69 { // NOLINT(whitespace/braces)
82 { // NOLINT(whitespace/braces)
448 auto lambda = [&] (Args... args) { f(*reg, args...); }; // NOLINT [readability/braces] [4]
475 auto lambda = [&] (Args... args) { f(shift, args...); }; // NOLINT [readability/braces] [4]
501 auto lambda = [&] (Args... args) { f(c, args...); }; // NOLINT [readability/braces] [4]
527 auto lambda = [&] (Args... args) { f(s, args...); }; // NOLINT [readability/braces] [4]
  /external/icu/icu4c/source/extra/uconv/
uconv.1.in 358 the litterature, delimited by curly braces for easy recognition of those
407 (The names are delimited by curly braces.
  /prebuilts/go/darwin-x86/src/go/build/
build_test.go 265 {"$SRCDIR is missing braces", "$SRCDIR is missing braces"},
  /prebuilts/go/linux-x86/src/go/build/
build_test.go 265 {"$SRCDIR is missing braces", "$SRCDIR is missing braces"},
  /art/runtime/lambda/
closure_builder.cc 160 ShortyFieldType shorty{shorty_types[i]}; // NOLINT [readability/braces] [4]
  /development/ndk/platforms/android-3/include/
pthread.h 226 * closing braces, and that using setjmp/longjmp/return/break/continue
  /development/ndk/platforms/android-5/include/
pthread.h 253 * closing braces, and that using setjmp/longjmp/return/break/continue
  /development/ndk/platforms/android-8/include/
pthread.h 258 * closing braces, and that using setjmp/longjmp/return/break/continue
  /external/ImageMagick/ImageMagick/script/
miff.html 62 <p>The MIFF header is composed entirely of ISO-8859-1 characters. The fields in the header are key and value combination in the <var>key = value</var> format, with each key and value separated by an equal sign (<code>=</code>). Each <var>key = value</var> combination is delimited by at least one control or whitespace character. Comments may appear in the header section and are always delimited by braces. The MIFF header always ends with a colon (<code>:</code>) character, followed by a <var>ctrl-Z</var> character. It is also common to proceed the colon with a <var>formfeed</var> and a <var>newline</var> character. The <var>formfeed</var> prevents the listing of binary data when using the <code>more</code> Unix program, whereas, the <var>ctrl-Z</var> has the same effect with the <code>type</code> command on the Windows command line.</p>
133 <td>defines a short title or caption for the image. If any whitespace appears in the label, it must be enclosed within braces.</td>
190 <p>Other key value pairs are permitted. If a value contains whitespace it must be enclosed with braces as illustrated here:</p>
202 <p>Note that <var>key = value</var> combinations may be separated by <var>newlines</var> or spaces and may occur in any order within the header. Comments (within braces) may appear anywhere before the colon.</p>

Completed in 683 milliseconds

1 2 34 5 6 7 8 91011>>