Home
last modified time | relevance | path

Searched refs:comments (Results 1 – 20 of 20) sorted by relevance

/system/tools/aidl/
Daidl_language.cpp361 const string& comments) in AidlTypeSpecifier() argument
366 comments_(comments), in AidlTypeSpecifier()
661 const std::string& comments) in AidlMethod() argument
662 : AidlMethod(location, oneway, type, name, args, comments, 0, true) { in AidlMethod()
668 const std::string& comments, int id, bool is_user_defined) in AidlMethod() argument
671 comments_(comments), in AidlMethod()
711 const std::string& comments, const std::string& package) in AidlDefinedType() argument
714 comments_(comments), in AidlDefinedType()
746 const std::string& package, const std::string& comments, in AidlParcelable() argument
748 : AidlDefinedType(location, name, comments, package), in AidlParcelable()
[all …]
Dparser.h34 AidlToken(const std::string& text, const std::string& comments) in AidlToken() argument
35 : text_(text), comments_(comments) {} in AidlToken()
Daidl_language.h188 void SetComments(const string& comments) { comments_ = comments; } in SetComments() argument
261 vector<unique_ptr<AidlTypeSpecifier>>* type_params, const string& comments);
573 vector<unique_ptr<AidlArgument>>* args, const string& comments);
575 vector<unique_ptr<AidlArgument>>* args, const string& comments, int id,
649 const std::string& comments, const std::string& package);
661 void SetComments(const std::string comments) { comments_ = comments; } in SetComments() argument
721 const std::string& comments, const std::string& cpp_header = "",
751 const std::string& package, const std::string& comments,
782 const std::string& comments);
811 const std::string& package, const std::string& comments);
[all …]
Daidl_language_y.yy265 // copy comments from annotation to decl
570 const std::string& comments = ($1->size() > 0) ? $1->begin()->GetComments() : $2->GetComments();
571 $$ = new AidlMethod(loc(@4), true, $3, $4->GetText(), $6, comments);
588 const std::string& comments = ($1->size() > 0) ? $1->begin()->GetComments() : $2->GetComments();
594 $$ = new AidlMethod(loc(@4), true, $3, $4->GetText(), $6, comments, serial);
650 // copy comments from annotation to type
/system/tools/hidl/test/hash_test/correct_hash/
Dcurrent.txt1 …20df49b684f3164f0a3f9aa18743a3521f3bd04e4a06fed64 test.hash.hash@1.0::IHash # comments are fine too
/system/tools/hidl/lint/test/interfaces/unhandled_comments/1.0/
DISingleComment.hal19 // All single line comments are unhandled
/system/core/init/
Dtokenizer_test.cpp78 TEST(tokenizer, comments) { in TEST() argument
DREADME.md13 Lines which start with a `#` (leading whitespace allowed) are comments.
/system/sepolicy/
DREADME63 is stripped of comments and whitespace. This is to preserve space on the
73 keys.conf. This tool is also responsible for stripping the comments and
/system/libhidl/transport/base/1.0/
DIBase.hal107 * @return info debugging information. See comments of DebugInfo.
/system/update_engine/
Dpylintrc132 # Ignore comments when computing similarities.
133 ignore-comments=yes
222 # (2) URLs in comments or pydocs. Detecting URLs by regex is a hard problem and
/system/tools/mkbootimg/
Dpylintrc104 # Ignore comments when computing similarities.
105 ignore-comments=yes
/system/tools/hidl/c2hal/
Dc2hal_l.ll148 // strings or comments in the function.
/system/core/libpixelflinger/codeflinger/
DGGLAssembler.cpp458 static char const * comments[] = {"alpha", "red", "green", "blue"}; in build_component() local
459 comment(comments[component]); in build_component()
/system/media/audio_utils/
DDoxyfile.orig168 # style comments (thus requiring an explicit @brief command for a brief
176 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
183 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
188 # Note that setting this tag to YES also means that rational rose comments are
275 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
905 # Fortran comments will always remain visible.
2023 # You can define message sequence charts within doxygen comments using the \msc
DDoxyfile.bak168 # style comments (thus requiring an explicit @brief command for a brief
176 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
183 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
188 # Note that setting this tag to YES also means that rational rose comments are
275 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
905 # Fortran comments will always remain visible.
2023 # You can define message sequence charts within doxygen comments using the \msc
DDoxyfile184 # style comments (thus requiring an explicit @brief command for a brief
194 # Javadoc-style will behave just like regular comments and it will not be
202 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
209 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
214 # Note that setting this tag to YES also means that rational rose comments are
318 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
995 # Fortran comments will always remain visible.
/system/chre/chre_api/doc/
DDoxyfile176 # style comments (thus requiring an explicit @brief command for a brief
184 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
191 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
196 # Note that setting this tag to YES also means that rational rose comments are
286 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
946 # Fortran comments will always remain visible.
2107 # You can define message sequence charts within doxygen comments using the \msc
/system/chre/pal/doc/
DDoxyfile176 # style comments (thus requiring an explicit @brief command for a brief
184 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
191 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
196 # Note that setting this tag to YES also means that rational rose comments are
286 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
946 # Fortran comments will always remain visible.
2107 # You can define message sequence charts within doxygen comments using the \msc
/system/timezone/input_data/android/
Dcountryzones.txt137 # only used when there is otherwise a tie. See comments for each country below