Searched +refs:google +refs:c +refs:style (Results 1 – 25 of 1036) sorted by relevance
12345678910>>...42
16 package com.google.android.exoplayer2.text.webvtt;20 import com.google.android.exoplayer2.text.span.TextAnnotation;21 import com.google.android.exoplayer2.util.Assertions;22 import com.google.android.exoplayer2.util.ColorParser;23 import com.google.android.exoplayer2.util.Log;24 import com.google.android.exoplayer2.util.ParsableByteArray;25 import com.google.android.exoplayer2.util.Util;26 import com.google.common.base.Ascii;95 WebvttCssStyle style = new WebvttCssStyle(); in parseBlock() local96 applySelectorToStyle(style, selector); in parseBlock()[all …]
15 package com.google.googlejavaformat.java;17 import static com.google.common.base.Preconditions.checkArgument;20 import com.google.common.collect.ImmutableList;21 import com.google.common.collect.Lists;103 for (Comment c : Lists.reverse(t.comments)) { in getTokens()104 if (last < c.getSourcePos(0)) { in getTokens()105 tokens.add(new RawTok(null, null, last, c.getSourcePos(0))); in getTokens()108 new RawTok(null, null, c.getSourcePos(0), c.getSourcePos(0) + c.getText().length())); in getTokens()109 last = c.getSourcePos(0) + c.getText().length(); in getTokens()168 protected Comment processComment(int pos, int endPos, CommentStyle style) { in processComment() argument[all …]
4 Every major open-source project has its own style guide: a set of conventions7 consistent style.11 ([google/styleguide](https://github.com/google/styleguide)) links to the12 style guidelines we use for Google code. If you are modifying a project that13 originated at Google, you may be pointed to this page to see the style guides21 also contains [cpplint][cpplint], a tool to assist with style guide compliance,22 and [google-c-style.el][emacs], an Emacs settings file for Google style.25 Document Format Style Guide][xml] may be helpful. In addition to actual style29 The style guides in this project are licensed under the CC-By 3.0 License,33 The following Google style guides live outside of this project:[all …]
1 # WebRTC coding style guide8 Some older parts of the code violate the style guide in various ways.14 WebRTC follows the [Chromium C++ style guide][chr-style] and the15 [Google C++ style guide][goog-style]. In cases where they conflict, the Chromium16 style guide trumps the Google style guide, and the rules in this file trump them19 [chr-style]: https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++.md20 [goog-style]: https://google.github.io/styleguide/cppguide.html27 Chromium; see the [list of banned C++ features in Chromium][chr-style-cpp].31 [chr-style-cpp]: https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++-features.…56 [examples and exceptions on how to treat `.h` and `.cpp` files](style-guide/h-cc-pairs.md).[all …]
37 the CL fulfills WebRTC style guides, language mastery, testability and49 1. If you are going to write in C++ make yourself familiar with with C++ style52 * [Google style guide][5]53 * [Chromium style guide][2]54 * [WebRTC style guide][3]79 [2]: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/styleguide/c++/c++.md80 [3]: https://webrtc.googlesource.com/src/+/refs/heads/main/g3doc/style-guide.md81 [4]: https://developers.google.com/open-source/cla/individual?hl=en82 [5]: https://google.github.io/styleguide/cppguide.html
35 import com.google.android.exoplayer.text.CaptionStyleCompat;36 import com.google.android.exoplayer.util.Util;172 public void setStyle(CaptionStyleCompat style) { in setStyle() argument173 mForegroundColor = style.foregroundColor; in setStyle()174 mBackgroundColor = style.backgroundColor; in setStyle()175 mEdgeType = style.edgeType; in setStyle()176 mEdgeColor = style.edgeColor; in setStyle()177 setTypeface(style.typeface); in setStyle()178 super.setBackgroundColor(style.windowColor); in setStyle()259 protected void onDraw(Canvas c) { in onDraw() argument[all …]
26 import com.google.ux.material.libmonet.dynamiccolor.DynamicScheme;27 import com.google.ux.material.libmonet.hct.Hct;28 import com.google.ux.material.libmonet.scheme.SchemeContent;29 import com.google.ux.material.libmonet.scheme.SchemeExpressive;30 import com.google.ux.material.libmonet.scheme.SchemeFruitSalad;31 import com.google.ux.material.libmonet.scheme.SchemeMonochrome;32 import com.google.ux.material.libmonet.scheme.SchemeNeutral;33 import com.google.ux.material.libmonet.scheme.SchemeRainbow;34 import com.google.ux.material.libmonet.scheme.SchemeTonalSpot;35 import com.google.ux.material.libmonet.scheme.SchemeVibrant;[all …]
9 import com.google.common.collect.ImmutableList;10 import com.google.common.collect.ImmutableMap;11 import com.google.common.collect.ImmutableSet;12 import com.google.common.collect.ImmutableSet.Builder;188 for (CommentType c : CommentType.values()) { in Comments()189 comments.put(c, new HashMap<String, String>()); in Comments()193 public String getComment(CommentType style, String xpath) { in getComment() argument194 return comments.get(style).get(xpath); in getComment()197 public Comments addComment(CommentType style, String xpath, String comment) { in addComment() argument198 String existing = comments.get(style).get(xpath); in addComment()[all …]
48 * Minijail uses kernel coding style:49 ….kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst50 * Utility functions with no side-effects should go in `util.{h|c}`.53 in `system.{h|c}`.60 We follow the [Google Markdown style guide].65 For style guides, check out the [Linux man-pages project] for general guidance.73 Please keep it in sync with [minijail0_cli.c].80 [minijail0_cli.c]: ./minijail0_cli.c85 [Google Markdown style guide]: https://github.com/google/styleguide/blob/gh-pages/docguide/style.md86 [Google Test]: https://github.com/google/googletest
9 .. image:: https://github.com/google/yapf/actions/workflows/ci.yml/badge.svg10 :target: https://github.com/google/yapf/actions13 .. image:: https://coveralls.io/repos/google/yapf/badge.svg?branch=main14 :target: https://coveralls.io/r/google/yapf?branch=main29 conforms to the style guide, even if the original code didn't violate the30 style guide. The idea is also similar to the `'gofmt' <https://golang.org/cmd/33 whenever modifications are made, the style remains consistent throughout the34 project and there's no point arguing about style in every code review.37 programmer would write if they were following the style guide. It takes away94 [--style STYLE] [--style-help] [--no-local-style] [-p][all …]
7 as some basic style discussions.23 .. code-block:: c++31 formatting. A list of options can be found under :ref:`style-options`. 39 The style options describe specific formatting options that can be used in40 order to make `ClangFormat` comply with different style guides. Currently,41 two style guides are hard-coded:43 .. code-block:: c++45 /// \brief Returns a format style complying with the LLVM coding standards:49 /// \brief Returns a format style complying with Google's C++ style guide:50 /// http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml.[all …]
5 :doc:`ClangFormatStyleOptions` describes configurable formatting style options11 custom style by configuring specific style options.17 :program:`clang-format` supports two ways to provide custom style options:18 directly specify style configuration in the ``-style=`` command line option or19 use ``-style=file`` and put style configuration in the ``.clang-format`` or22 When using ``-style=file``, :program:`clang-format` for each input file will40 language set, it will set the default style options for all lanugages.55 # We'll use defaults from the LLVM style, but with 4 columns indentation.74 options of a certain predefined style is:78 clang-format -style=llvm -dump-config > .clang-format[all …]
... , int, java.lang.Character) Character style public java.lang.Character getChar () public ...
14 google-java-format = ${REPO_ROOT}/prebuilts/tools/common/google-java-format/google-java-format15 google-java-format-diff = ${REPO_ROOT}/prebuilts/tools/common/google-java-format/google-java-format…19 clang_format = --commit ${PREUPLOAD_COMMIT} --style file --extensions c,h,cc,cpp21 ktfmt = --kotlinlang-style
4 [](https://travis-ci.org/go…69 ../src/google/protobuf/descriptor.proto95 the enum's name (so the referencing code is in Java style).148 enum_style -> c or java215 Defines the style of the generated code for fields.219 In the default style, optional fields translate into public mutable228 return value determines whether a field is serialized, so this style is232 In the 'accessors' style, required and nested message fields are still236 IMPORTANT: When using the 'accessors' style, ProGuard should always249 In the 'reftypes' style, fields are initialized to null (or empty[all …]
1 # C style guide9 [Google C++ style guide](https://google.github.io/styleguide/cppguide.html) with12 Everything written here is intended to follow the spirit of the C++ style guide.25 ```c++33 ```c++43 ```c++54 ```c++
2 # Use of this source code is governed by a BSD-style license that can be103 "adler32_simd.c",114 "adler32_simd.c",158 "crc32_simd.c",196 "contrib/optimizations/inffast_chunk.c",198 "contrib/optimizations/inflate.c",205 # style function declarations, which triggers warning C4131.226 "crc32_simd.c",228 "crc_folding.c",290 "adler32.c",[all …]
74 follows the [Google C++ style][google-cpp-style], and targets `-std=c++17`.79 https://github.com/google/perfetto is an up-to-date and actively maintained122 Mailing list: https://groups.google.com/forum/#!forum/perfetto-dev125 [Google's Open Source Community Guidelines](https://opensource.google/conduct/).131 * **Googlers**: use the internal bug tracker [go/perfetto-bugs](http://goto.google.com/perfetto-bug…132 * **Non-Googlers**: use [GitHub issues](https://github.com/google/perfetto/issues).143 part of the project. Head over to <https://cla.developers.google.com/> to see151 [google-cpp-style]: https://google.github.io/styleguide/cppguide.html153 [ci-example]: https://android-review.googlesource.com/c/platform/external/perfetto/+/1108253/3#mess…
3 …rary follows the [Chromium C++ coding style](https://chromium.googlesource.com/chromium/src/+/main…4 which, in turn, defers to the [Google C++ Style Guide](https://google.github.io/styleguide/cppguide…5 … the [Chromium C++ Do's and Don'ts](https://sites.google.com/a/chromium.org/dev/developers/coding-…16 Blink style is *not allowed* anywhere in the Open Screen Library.41 - Braces are optional for single-line if statements; follow the style of67 … the use of `default` and `delete`](https://sites.google.com/a/chromium.org/dev/developers/coding-…106 Ref: [Google Style Guide on Rvalue References](https://google.github.io/styleguide/cppguide.html#Rv…113 TODO(https://issuetracker.google.com/issues/160731444): Enforce this191 …K/CHECK](https://chromium.googlesource.com/chromium/src/+/main/styleguide/c++/c++.md#check_dcheck_…
1 …adge/Slack-ktfmt-purple.svg?logo=slack)](https://slack-chats.kotlinlang.org/c/ktfmt) [.48 [`.editorconfig` file](https://www.jetbrains.com/help/idea/configuring-code-style.html#editorconfig)70 java -jar /path/to/ktfmt-<VERSION>-jar-with-dependencies.jar [--kotlinlang-style | --google-style] …73 `--kotlinlang-style` makes `ktfmt` use a block indent of 4 spaces instead of 2.104 `ktfmt` uses google-java-format's underlying engine, and as such, many items on105 [google-java-format's FAQ](https://github.com/google/google-java-format/wiki/FAQ) apply to `ktfmt`112 …https://github.com/google/google-java-format/wiki/FAQ#i-just-need-to-configure-it-a-bit-differentl…114 1. For exposed configurations, like `style`, we aim to make sure that those are easily shared129 2. From a pragmatic standpoint, the formatting engine behind google-java-format uses more whitespace[all …]
... -INF/MANIFEST.MF com/ com/google/ com/google/googlejavaformat/ com/google
1 .. _docs-pw-style-cpp:4 C++ style6 The Pigweed C++ style guide is closely based on Google's external C++ Style8 https://google.github.io/styleguide/cppguide.html. The Google C++ Style Guide11 The Pigweed style guide only applies to Pigweed itself. It does not apply to17 Pigweed style guide, but are separated out since it covers more general18 embedded development beyond just C++ style.22 All Pigweed C++ code must compile with ``-std=c++17`` in Clang and GCC. C++20110 * C Standard Library headers (``<c*>``)176 Prefer C++-style (``//``) comments over C-style comments (``/* */``). C-style[all …]