OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:strong
(Results
2076 - 2100
of
3412
) sorted by null
<<
81
82
83
84
85
86
87
88
89
90
>>
/external/owasp/sanitizer/tools/findbugs/doc/ja/manual/
analysisprops.html
3
<title>第9章 分析プロパティー</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="FindBugs™ マニュアル"><link rel="up" href="index.html" title="FindBugs™ マニュアル"><link rel="prev" href="filter.html" title="第8章 フィルターファイル"><link rel="next" href="annotations.html" title="第10章 アノテーション"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">第9章 分析プロパティー</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="filter.html">戻る</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="annotations.html">次へ</a></td></tr></table><hr></div><div class="chapter" title="第9章 分析プロパティー"><div class="titlepage"><div><div><h2 class="title"><a name="analysisprops"></a>第9章 分析プロパティー</h2></div></div></div><p><span class="application">FindBugs</span> は分析する場合にいくつかの観点を持っています。そして、観点をカスタマイズして実行することができます。システムプロパティーを使って、それらのオプションを設定します。この章では、分析オプションの設定方法を説明します。</p><p>分析オプションの主な目的は、 2 つあります。1 番目は、 <span class="application">FindBugs</span> に対して分析されるアプリケーションのメソッドの意味を伝えることです。そうすることで <span class="application">FindBugs</span> がより正確な結果を出すことができ、誤検出を減らすことができます。2 番目に、分析を行うに当たりその精度を設定できるようにすることです。分析の精度を落とすことで、メモリ使用量と分析時間を減らすことができます。ただし、本当のバグを見逃したり、誤検出の数が増えるという代償があります。</p><p>コマンドラインオプション <span class="command"><
strong
>-property</
strong
></span> を使って、分析オプションを設定することができます。次に、例を示します:</p><pre class="screen">
4
<code class="prompt">$ </code><span class="command"><
strong
>findbugs -textui -property "cfg.noprune=true" <em class="replaceable"><code>myApp.jar</code></em></
strong
></span>
/external/qemu/distrib/sdl-1.2.15/docs/html/
joystick.html
167
>Joysticks, and other similar input devices, have a very
strong
role in game playing and SDL provides comprehensive support for them. Axes, Buttons, POV Hats and trackballs are all supported.</P
sdllistmodes.html
167
> and they play a
strong
role in deciding what modes are valid. For instance, if you pass <TT
/external/valgrind/main/none/tests/x86/
bug152818-x86.c
11
* guess 1 (
strong
:]):
/external/zlib/src/contrib/minizip/
crypt.h
26
http://www.winzip.com/aes_info.htm ) and PKWare PKZip 5.x
Strong
/frameworks/base/core/java/android/net/
NetworkIdentity.java
32
* Network definition that includes
strong
identity. Analogous to combining
/frameworks/base/core/java/android/view/inputmethod/
EditorInfo.java
252
* <p>Also, this needs to be the cursor position <
strong
>right now</
strong
>,
268
* <p>Also, this needs to be the cursor position <
strong
>right now</
strong
>,
/frameworks/base/core/jni/
android_hardware_Camera.cpp
87
jclass mCameraJClass; //
strong
reference to java class
88
sp<Camera> mCamera; //
strong
reference to native object
89
jclass mFaceClass; //
strong
reference to Face class
90
jclass mRectClass; //
strong
reference to Rect class
[
all
...]
android_view_RenderNodeAnimator.cpp
50
// This holds a
strong
reference to a Java WeakReference<T> object. This avoids
/frameworks/base/docs/html/guide/practices/
compatibility.jd
164
<p class="note"><
strong
>Note:</
strong
> Some <a href=
218
<p class="note"><
strong
>Note:</
strong
>
/frameworks/base/docs/html/guide/topics/connectivity/usb/
host.jd
47
<p class="table-caption"><
strong
>Table 1.</
strong
> USB Host APIs</p>
289
<p class="note"><
strong
>Note:</
strong
> If your application <a href="#using-intents">uses an
/frameworks/base/docs/html/tools/support-library/
features.jd
165
<p class="note"><
strong
>Note:</
strong
>
344
<
strong
>Note:</
strong
> Use of RenderScript with the support library is supported with the Android
/frameworks/base/docs/html/training/contacts-provider/
display-contact-badge.jd
189
<
strong
>Note:</
strong
> The
505
<
strong
>Note:</
strong
> The following code snippets use the method
/frameworks/base/docs/html/training/game-controllers/
compatibility.jd
68
<
strong
>Table 1.</
strong
> APIs for game controller support across
295
<
strong
>Figure 1.</
strong
> Class diagram of interface and version-specific
/frameworks/base/docs/html/training/location/
receive-location-updates.jd
96
<
strong
>Note:</
strong
> To make your app compatible with
448
<
strong
>Note:</
strong
> If your app accesses the network or does other long-running work after
/frameworks/base/docs/html/training/sync-adapters/
running-sync-adapter.jd
116
<
strong
>Note:</
strong
> If you use GCM to trigger your sync adapter via a broadcast to all
181
<
strong
>Note:</
strong
> If you're using a stub content provider, you don't have any data in
/frameworks/native/include/binder/
IBinder.h
108
* binder. You should not try to promote this to a
strong
reference.
/frameworks/support/v4/java/android/support/v4/view/accessibility/
AccessibilityRecordCompat.java
596
* <
strong
>Note:</
strong
> It is a client responsibility to recycle the
1007
* <
strong
>Note:</
strong
> You must not touch the object after calling this
/frameworks/support/v7/mediarouter/src/android/support/v7/media/
RemoteControlClientCompat.java
164
// the volume callback from holding
strong
references to anything important.
/frameworks/wilhelm/src/android/
android_StreamPlayer.h
55
// Call at least once prior to releasing the last
strong
reference to this object. It causes
/libcore/dom/src/test/java/org/w3c/domts/level1/core/
hc_elementinvalidcharacterexception.java
36
* "
strong
" containing an invalid character.
hc_namednodemapnotfounderr.java
33
* named "
strong
" in the map.
hc_namednodemapwrongdocumenterr.java
77
String
strong
;
local
hc_nodeappendchildchildexists.java
78
expected.add("
strong
");
hc_nodeappendchilddocfragment.java
81
expected.add("
strong
");
Completed in 637 milliseconds
<<
81
82
83
84
85
86
87
88
89
90
>>