| /packages/apps/UnifiedEmail/src/com/google/android/mail/common/html/parser/ |
| HTML4.java | 93 return addElement(tag, flags, HTML.Element.Flow.NONE);
97 private static HTML.Element addElement(String tag, String flags, HTML.Element.Flow flow) {
98 return addElement(tag, flags, flow, HTML.Element.NO_TYPE);
102 private static HTML.Element addTableElement(String tag, String flags, HTML.Element.Flow flow) {
103 return addElement(tag, flags, flow, HTML.Element.TABLE_TYPE);
107 private static HTML.Element addElement(String tag, String flags, HTML.Element.Flow flow,
122 HTML.Element element = new HTML.Element(tag, type, empty, optionalEndTag, breaksFlow, flow);
[all...] |
| HTML.java | 46 public enum Flow {
57 private final Flow flow; field in class:HTML.Element
62 * NOTE: Even though breaksFlow and flow are named similarly, they're not quite the same thing.
63 * Flow refers to whether the element is inherently character or block level. Breaks flow
66 * @throws IllegalArgumentException if name or flow is null.
69 boolean optionalEndTag, boolean breaksFlow, Flow flow) {
71 Preconditions.checkNotNull(flow, "Element flow can not be null")
[all...] |
| /external/llvm/lib/Transforms/Scalar/ |
| StructurizeCFG.cpp | 53 static const char *const FlowBlockName = "Flow";
118 /// @brief Transforms the control flow graph on one single entry/exit region
121 /// After the transform all "If"/"Then"/"Else" style control flow looks like
135 /// | / 3 = "Flow" blocks, newly inserted flow blocks, rejoins the flow
137 /// 5 5 = "End" block, also rejoins the control flow
140 /// Control flow is expressed as a branch where the true exit goes into the
154 /// |/ 2 = "Loop" optional subregion, with all exits at "Flow" block
155 /// 3 3 = "Flow" block, with back edge to entry bloc
[all...] |
| /external/iproute2/doc/ |
| api-ip6-flowlabels.tex | 2 \def\TITLE{IPv6 Flow Labels}
5 \Large\bf IPv6 Flow Labels in Linux-2.2.
22 Every IPv6 packet carries 28 bits of flow information. RFC2460 splits
24 prefer this term) and 20 bits of flow label. Currently there exist
25 no well-defined API to manage IPv6 flow information. In this document
42 \item To assign flow labels to packets sent by user.
44 \item To get flow labels of received packets. I do not know
46 want to use flow labels to distinguish sub-flows.
48 \item To allocate flow labels in the way, compliant to RFC2460. Namely:
52 Flow labels must be uniformly distributed (pseudo-)random numbers
[all...] |
| /build/tools/droiddoc/templates-ndk/assets/js/ |
| docs.js | [all...] |
| /build/tools/droiddoc/templates-sdk-dev/assets/js/ |
| docs.js | [all...] |
| /build/tools/droiddoc/templates-sdk/assets/js/ |
| docs.js | [all...] |
