Searched +refs:google +refs:set +refs:c +refs:style (Results 1 – 25 of 924) sorted by relevance
12345678910>>...37
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 …]
4 [](https://travis-ci.org/go…69 ../src/google/protobuf/descriptor.proto95 the enum's name (so the referencing code is in Java style).122 set and therefore is not serialized. Consider the situation where we148 enum_style -> c or java201 repeated fields, groups or messages). It is set to false initially203 it is set to true. This is a way for clients to inspect the "has"204 value upon parse. If it is set to true, writeTo(...) will ALWAYS215 Defines the style of the generated code for fields.219 In the default style, optional fields translate into public mutable[all …]
65 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-75 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII76 # characters to appear in the names of generated files. If set to NO, non-ASCII98 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member105 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief108 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the125 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then132 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all140 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path141 # before files name in the file list and in the header files. If set to NO the[all …]
63 OUTPUT_DIRECTORY = doc/ref/c++.internal65 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-75 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII76 # characters to appear in the names of generated files. If set to NO, non-ASCII98 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member105 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief108 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the125 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then132 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all140 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path[all …]
1 .. _docs-style-rest:4 reStructuredText style guide11 This style guide defines Pigweed's conventions for `reStructuredText`_ (reST).15 .. tip:: ``pw format`` detects reST style issues.17 .. _docs-style-rest-overview:23 .. _docs-style-rest-scope:27 This style guide applies to all reST markup that's intended to be published to31 .. _docs-style-rest-other:33 Related style guides35 This style guide is narrowly focused on Pigweed's usage of reStructuredText.[all …]
1 .. _docs-pw-style-cli:4 CLI style10 The Pigweed CLI style guide is based on the `Command Line Interface Guidelines18 The Pigweed CLI style guide only applies to utilities included in Pigweed25 The following programs demonstrate conformance to Pigweed's CLI style guide rules:28 <https://cs.opensource.google/pigweed/pigweed/+/main:pw_digital_io_linux/digital_io_cli.cc>`_63 .. tab-set-code::65 .. code-block:: c++74 .. code-block:: c94 .. tab-set-code::[all …]
1 .. _docs-style-doxygen:4 Doxygen style guide10 called **Doxygen comments**. This style guide shows you how to format Doxygen13 .. _docs-style-doxygen-quickstart:24 .. _//pw_i2c/public/pw_i2c/device.h: https://cs.opensource.google/pigweed/pigweed/+/4c1a7158b663f11…27 .. _//pw_i2c/reference.rst: https://cs.opensource.google/pigweed/pigweed/+/4c1a7158b663f114c297d9c0…28 .. _//docs/BUILD.gn: https://cs.opensource.google/pigweed/pigweed/+/4c1a7158b663f114c297d9c0a806f41…41 :ref:`docs-style-doxygen-breathe-overview` for more explanation.51 .. _docs-style-doxygen-writing:54 API reference writing style[all …]
1 # Copyright (c) Facebook, Inc. and its affiliates.4 # This source code is licensed under the BSD-style license found in the15 set(CLOG_RUNTIME_TYPE "default" CACHE STRING "Type of runtime library (shared, static, or default) …42 set(CONFU_DEPENDENCIES_SOURCE_DIR ${CMAKE_SOURCE_DIR}/deps43 CACHE PATH "Confu-style dependencies source directory")44 set(CONFU_DEPENDENCIES_BINARY_DIR ${CMAKE_BINARY_DIR}/deps45 CACHE PATH "Confu-style dependencies binary directory")55 …set(GOOGLETEST_SOURCE_DIR "${CONFU_DEPENDENCIES_SOURCE_DIR}/googletest" CACHE STRING "Google Test …60 add_library(clog STATIC src/clog.c)86 # ---[ Build google test[all …]
... , int, java.lang.Character) Character style public java.lang.Character getChar () public ...
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 …]
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 …]
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.41 Configuration sections for specific language will override options set in the55 # We'll use defaults from the LLVM style, but with 4 columns indentation.74 options of a certain predefined style is:[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++62 uint64_t _mask; // Bits are set for acceptable value 0 <= x < 64
3 [](https://docs.rs/c…4 …github/actions/workflow/status/google/coset/ci.yml?branch=main&color=blue&style=for-the-badge)](ht…5 …codecov](https://img.shields.io/codecov/c/github/google/coset?style=for-the-badge)](https://codeco…7 This crate holds a set of Rust types for working with CBOR Object Signing and Encryption (COSE) obj…22 This crate supports `no_std` (when the `std` feature is not set, which is the default), but uses th…
2 # Use of this source code is governed by a BSD-style15 …file(DOWNLOAD "https://github.com/google/googletest/archive/master.zip" ${CMAKE_SOURCE_DIR}/master…27 set(CMAKE_SUPPRESS_DEVELOPER_WARNINGS 1 CACHE INTERNAL "No dev warnings")32 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -Wno-narrowing")34 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 -Wno-c++11-narrowing")47 set(EXTRA_TARGET_LINK_LIBRARIES)51 set(THREADING threadwin)53 set(THREADING thread)57 set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)58 set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)[all …]
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 …]
88 .. c:macro:: PW_LOG(level, verbosity, module, flags, fmt, ...)129 ``PW_LOG_DEBUG`` style macros, which are often implemented more efficiently134 .. c:macro:: PW_LOG_DEBUG(fmt, ...)135 .. c:macro:: PW_LOG_INFO(fmt, ...)136 .. c:macro:: PW_LOG_WARN(fmt, ...)137 .. c:macro:: PW_LOG_ERROR(fmt, ...)138 .. c:macro:: PW_LOG_CRITICAL(fmt, ...)142 .. c:macro:: PW_LOG_EVERY_N(level, rate, ...)151 .. c:macro:: PW_LOG_EVERY_N_DURATION(level, min_interval_between_logs, msg, ...)201 .. c:macro:: PW_LOG_LEVEL_DEFAULT[all …]
1 # Copyright (c) 2009-2021, Google LLC4 # Use of this source code is governed by a BSD-style6 # https://developers.google.com/open-source/licenses/bsd53 "generated-in/google/protobuf/descriptor.upb.h",54 "generated-in/google/protobuf/descriptor.upb_minitable.c",55 "generated-in/google/protobuf/descriptor.upb_minitable.h",57 cmd = "cp $(SRCS) $(@D)/generated-in/google/protobuf",64 "google/protobuf/descriptor.upb.h",65 "google/protobuf/descriptor.upb_minitable.c",66 "google/protobuf/descriptor.upb_minitable.h",[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 maintained108 Both CIs are kicked in when the `Presubmit-Ready: +1` is set and will publish a122 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…
10 * Behavior changes and anything nontrivial (i.e. anything other than simple cleanups and style15 [ANGLE-website]: https://groups.google.com/forum/?fromgroups#!forum/angleproject23 1. Must conform to the [ANGLE style][ANGLE-style] guidelines.27 [ANGLE-style]: CodingStandard.md56 * To kick off a try job, use the 'CQ Dry Run' button, or set the Commit-Queue +1 label to trigger95 [Chrome-Canary]: https://www.google.com/chrome/browser/canary.html114 [Individual-CLA]: https://cla.developers.google.com/about/google-individual115 [Corporate-CLA]: https://cla.developers.google.com/about/google-corporate124 3. Follow the directions on the new-password page to set up authentication with your Google account.125 4. Make sure to set your real name.[all …]
2 # Use of this source code is governed by a BSD-style5 # https://github.com/google/oss-policies-info/blob/main/foundational-cxx-support-matrix.md19 # See https://groups.google.com/g/re2-dev/c/P6_NM0YIWvA for details.29 set(REQUIRES)33 set(SONAME 11)35 set(EXTRA_TARGET_LINK_LIBRARIES)42 set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON)58 set(THREADS_PREFER_PTHREAD_FLAG ON)62 set(ABSL_DEPS100 set(RE2_SOURCES[all …]