/prebuilts/misc/common/swig/include/2.0.11/ |
swig.swg | 259 %rename("$ignore", %$isenumitem, %$classname="MyClass") "";
|
/prebuilts/ndk/8/sources/cxx-stl/gnu-libstdc++/4.7/include/ |
istream | 840 * MyClass mc;
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.7/include/ |
istream | 840 * MyClass mc;
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.8/include/ |
istream | 846 * MyClass mc;
|
/prebuilts/ndk/9/sources/cxx-stl/gnu-libstdc++/4.9/include/ |
istream | 846 * MyClass mc;
|
/external/clang/include/clang/ASTMatchers/ |
ASTMatchers.h | 17 // recordDecl(hasName("MyClass")) 19 // a class named 'MyClass'. 28 // recordDecl(hasName("MyClass"), hasChild(id("child", recordDecl()))) [all...] |
/external/clang/lib/Sema/ |
SemaDeclObjC.cpp | 566 // @interface MyClass : SuperClass {} @end [all...] |
/external/chromium_org/native_client_sdk/doc_generated/pepper_beta/cpp/ |
classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p> [all...] |
/external/chromium_org/native_client_sdk/doc_generated/pepper_dev/cpp/ |
classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p> [all...] |
/external/chromium_org/native_client_sdk/doc_generated/pepper_stable/cpp/ |
classpp_1_1_file_i_o.html | 274 <p>So you must ensure that your buffer outlives the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource. If you have one class and use the <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource exclusively from that class and never make any copies, this will be fine: the resource will be destroyed when your class is. But keep in mind that copying a <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> object just creates a second reference to the original resource. For example, if you have a function like this: <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">pp::FileIO</a> MyClass::GetFileIO(); where a copy of your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource could outlive your class, the callback will still be pending when your class goes out of scope, creating the possibility of writing into invalid memory. So it's recommended to keep your <a class="el" href="classpp_1_1_file_i_o.html" title="The FileIO class represents a regular file.">FileIO</a> resource and any output buffers tightly controlled in the same scope.</p> [all...] |
/frameworks/base/docs/html/training/articles/ |
perf-jni.jd | 169 <pre>jclass localClass = env->FindClass("MyClass"); [all...] |
/prebuilts/misc/common/swig/include/2.0.11/lua/ |
luarun.swg | 856 so you can do MyClass(...) as well as new_MyClass(...) [all...] |
/external/chromium_org/third_party/WebKit/Tools/Scripts/webkitpy/thirdparty/ |
pep8.py | 818 Okay: from myclas import MyClass 820 Okay: import myclass [all...] |
/external/valgrind/main/memcheck/ |
mc_leakcheck.c | 722 // We have a strange/wrong case for 'ptr = new MyClass[0];' : 728 // 0-sized block. This trick does not work for 'new MyClass[0]' [all...] |
/prebuilts/tools/common/easymock-tools/ |
easymock-3.1-tests.jar | |
/external/clang/include/clang/AST/ |
DeclObjC.h | [all...] |
/external/clang/test/SemaCXX/ |
warn-thread-safety-parsing.cpp | [all...] |
/external/owasp/sanitizer/tools/findbugs/doc/ja/manual/ |
running.html | 22 </p></div><div class="sect2" title="3.3. テキストユーザーインタフェースオプション"><div class="titlepage"><div><div><h3 class="title"><a name="d0e834"></a>3.3. テキストユーザーインタフェースオプション</h3></div></div></div><p>ここで示すオプションは、テキストユーザーインタフェースでのみ使用できます。</p><div class="variablelist"><dl><dt><span class="term"><span class="command"><strong>-sortByClass</strong></span></span></dt><dd><p>報告されるバグ検索結果をクラス名でソートします。</p></dd><dt><span class="term"><span class="command"><strong>-include</strong></span> <em class="replaceable"><code>filterFile.xml</code></em></span></dt><dd><p><em class="replaceable"><code>filterFile.xml</code></em> で指定したフィルターに一致したバグ検索結果のみ報告されます。<a class="xref" href="filter.html" title="第8章 フィルターファイル">8章<i>フィルターファイル</i></a> を参照してください。</p></dd><dt><span class="term"><span class="command"><strong>-exclude</strong></span> <em class="replaceable"><code>filterFile.xml</code></em></span></dt><dd><p><em class="replaceable"><code>filterFile.xml</code></em> で指定したフィルターに一致したバグ検索結果は報告されません。<a class="xref" href="filter.html" title="第8章 フィルターファイル">8章<i>フィルターファイル</i></a> を参照してください。</p></dd><dt><span class="term"><span class="command"><strong>-onlyAnalyze</strong></span> <em class="replaceable"><code>com.foobar.MyClass,com.foobar.mypkg.*</code></em></span></dt><dd><p>コンマ区切り& (…) [all...] |
/external/valgrind/main/helgrind/docs/ |
hg-manual.xml | [all...] |
/frameworks/base/docs/html/guide/faq/ |
commontasks.jd | [all...] |
/external/clang/lib/Analysis/ |
ThreadSafety.cpp | 398 // This is a pointer-to-member expression, e.g. &MyClass::mu_. [all...] |
/external/proguard/docs/manual/ |
usage.html | 183 "<code>mypackage.MyClass.class.getResource("")</code>". You'll then want to [all...] |
/prebuilts/tools/common/proguard/proguard4.7/docs/manual/ |
usage.html | 181 with constructs like "<code>MyClass.class.getResource("")</code>". If the [all...] |
/external/clang/unittests/Format/ |
FormatTest.cpp | [all...] |
/external/chromium_org/third_party/WebKit/PerformanceTests/Dromaeo/resources/dromaeo/web/tests/ |
cssquery-dojo.html | [all...] |