Searched refs:Java (Results 1 – 25 of 1263) sorted by relevance
12345678910>>...51
/external/javaparser/javaparser-core-testing/src/test/resources/com/github/javaparser/lexical_preservation_samples/ |
D | Example4_original.java.txt | 47 * Parse Java source code and creates Abstract Syntax Trees. 122 * Parses the Java code contained in the {@link InputStream} and returns a 125 * @param in {@link InputStream} containing Java source code 127 * @return CompilationUnit representing the Java source code 135 * Parses the Java code contained in the {@link InputStream} and returns a 139 * @param in {@link InputStream} containing Java source code 140 * @return CompilationUnit representing the Java source code 148 * Parses the Java code contained in a {@link File} and returns a 151 * @param file {@link File} containing Java source code 153 * @return CompilationUnit representing the Java source code [all …]
|
/external/protobuf/java/ |
D | lite.md | 7 ## Use Protobuf Java Lite Runtime 9 Protobuf Java Lite runtime is separated from the main Java runtime because 10 it's designed/implemented with different constraints. In particular, Java 15 NOT guarantee API/ABI stability for Java Lite. If this is not acceptable 16 for your use-case, please use the full Java runtime instead. Note that 17 the latest version of Java Lite is not compatible with the 3.0.0 version. 19 You can generate Java Lite code for your .proto files: 26 Include the generated Java files in your project and add a dependency on the 27 protobuf Java runtime. If you are using Maven, use the following: 37 For the older version of Java Lite (v3.0.0), please refer to:
|
D | README.md | 7 ## Use Java Protocol Buffers 9 To use protobuf in Java, first obtain the protocol compiler (a.k.a., protoc, 11 generate Java code for your .proto files: 15 Include the generated Java files in your project and add a dependency on the 16 protobuf Java runtime. 52 ### Use Java Protocol Buffers on Android 54 For Android users, it's recommended to use protobuf Java Lite runtime because 55 of its smaller code size. Java Lite runtime also works better with Proguard 56 because it doesn't rely on Java reflection and is optimized to allow as much 57 code stripping as possible. You can following these [instructions to use Java [all …]
|
/external/javaparser/javaparser-core-testing-bdd/src/test/resources/com/github/javaparser/ |
D | pretty_printing_scenarios.story | 7 When the class is parsed by the Java parser 22 When the class is parsed by the Java parser 46 When the class is parsed by the Java parser 69 When the class is parsed by the Java parser 89 When the class is parsed by the Java parser 112 When the class is parsed by the Java parser 129 When the class is parsed by the Java parser 139 When the class is parsed by the Java parser 155 When the class is parsed by the Java parser 173 When the class is parsed by the Java parser [all …]
|
D | comment_attribution_scenarios.story | 1 Scenario: A Class With Line Comments is processed by the Java Parser 15 When the class is parsed by the Java parser 26 Scenario: A Class With Line Comments is processed by the Java Parser 44 When the class is parsed by the Java parser 58 Scenario: A Class With Orphan Comment in Class Declaration is parsed by the Java Parser 70 When the class is parsed by the Java parser 75 Scenario: A Class With Line Comments in Multiple Methods is parsed by the Java Parser 97 When the class is parsed by the Java parser 113 Scenario: A Class With Line Comments in Multiple Methods is parsed by the Java Parser 130 When the class is parsed by the Java parser [all …]
|
/external/libchrome/base/android/jni_generator/ |
D | README.md | 2 JNI (Java Native Interface) is the mechanism that enables Java code to call 3 native functions, and native code to call Java functions. 5 * Native code calls into Java using apis from `<jni.h>`, which basically mirror 6 Java's reflection APIs. 7 * Java code calls native functions by declaring body-less functions with the 8 `native` keyword, and then calling them as normal Java functions. 14 `jni_generator` uses regular expressions to parse .Java files, so don't do 27 * Java->Native calls are exported from the shared library and lazily resolved 31 * Java->Native calls are explicitly registered with JNI on the native side. 47 ### Exposing Java Methods [all …]
|
/external/flatbuffers/docs/source/ |
D | JavaUsage.md | 1 Use in Java {#flatbuffers_guide_use_java} 6 Before diving into the FlatBuffers usage in Java, it should be noted that 8 general FlatBuffers usage in all of the supported languages (including Java). 10 specific to Java. 17 ## FlatBuffers Java code location 19 The code for the FlatBuffers Java library can be found at 24 ## Testing the FlatBuffers Java libraries 28 The test code for Java is located in [JavaTest.java](https://github.com/google 36 *Note: These scripts require that [Java](https://www.oracle.com/java/index.html) 39 ## Using the FlatBuffers Java library [all …]
|
/external/libxml2/result/ |
D | svg2.rde | 60 4 3 #text 0 1 Java Font definition:Dialog 0 71 4 3 #text 0 1 Java Font definition:Helvetica 0 99 4 3 #text 0 1 Java Font definition:Dialog 0 110 4 3 #text 0 1 Java Font definition:Helvetica 700 159 4 3 #text 0 1 Java Font definition:Dialog 700 170 4 3 #text 0 1 Java Font definition:Dialog 700
|
D | svg2.rdr | 60 4 3 #text 0 1 Java Font definition:Dialog 0 71 4 3 #text 0 1 Java Font definition:Helvetica 0 99 4 3 #text 0 1 Java Font definition:Dialog 0 110 4 3 #text 0 1 Java Font definition:Helvetica 700 159 4 3 #text 0 1 Java Font definition:Dialog 700 170 4 3 #text 0 1 Java Font definition:Dialog 700
|
/external/perfetto/docs/data-sources/ |
D | java-heap-profiler.md | 1 # Memory: Java heap profiler 3 NOTE: The Java heap profiler requires Android 11 or higher 6 started with Java heap profiling. 8 Conversely from the [Native heap profiler](native-heap-profiler.md), the Java 10 call-stacks. The information recorded by the Java heap profiler is of the form: 20 ![Java heap profiles in the process tracks](/docs/images/profile-diamond.png) 22 ![Flamegraph of a Java heap profiler](/docs/images/java-flamegraph.png) 26 Information about the Java Heap is written to the following tables: 34 bytes in the Java heap end up being primitive arrays or strings. 86 The Java heap profiler is configured through the
|
/external/apache-commons-bcel/docs/ |
D | manual.bib | 11 title = {\protect{Adding Type Parameterization to the Java 30 title = {\protect{Barat -- A Front-End for Java}}, 47 title = {\protect{BIT: A Tool for Instrumenting Java 72 title = {\protect{Dynamic Class Loading in the Java Virtual 98 title = {The Java Language Specification}, 104 title = {Inside Java Class Files}, 114 title = {Java Virtual Machine}, 121 title = {\protect{JaWa: Java with Assertions}}, 138 title = {The Java Virtual Machine Specification}, 145 title = {\protect{Parameterized Types for Java}}, [all …]
|
D | generic.mdl | 78 language "Java") 108 language "Java") 129 language "Java") 143 language "Java") 151 language "Java") 164 language "Java") 177 language "Java") 185 language "Java") 193 language "Java") 203 language "Java") [all …]
|
/external/opencensus-java/contrib/agent/ |
D | README.md | 1 # OpenCensus Agent for Java 7 The *OpenCensus Agent for Java* collects and sends latency data about your Java process to 13 The *OpenCensus Agent for Java* is in an early development stage. The following features are 40 We see tracing as a cross-cutting concern which the *OpenCensus Agent for Java* weaves into 41 existing Java bytecode (the application and its libraries) at runtime, typically when first loading 48 stays as-is across the supported versions, the Java agent's bytecode weaver will be able to 51 The *OpenCensus Agent for Java* uses [Byte Buddy](http://bytebuddy.net/), a widely used and 52 well-maintained bytecode manipulation library, for instrumenting selected Java methods at class 53 load-time. Which Java methods we want to intercept/instrument obviously depends on the library 59 Download the latest version of the *OpenCensus Agent for Java* `.jar` file [all …]
|
/external/grpc-grpc-java/compiler/ |
D | README.md | 1 gRPC Java Codegen Plugin for Protobuf Compiler 4 This generates the Java interfaces out of the service definition from a 15 * Java 7 or up 35 To compile a proto file and generate Java interfaces out of the service definitions: 40 To generate Java interfaces with protobuf lite: 45 To generate Java interfaces with protobuf nano: 59 ## Creating a release of GRPC Java
|
/external/javassist/ |
D | README.md | 1 Java bytecode engineering toolkit 6 Javassist (JAVA programming ASSISTant) makes Java bytecode manipulation 7 simple. It is a class library for editing bytecodes in Java; it enables Java 12 of the Java bytecode. The whole API is designed with only the vocabulary of 13 the Java language. You can even specify inserted bytecode in the form of
|
/external/icu/icu4j/tools/build/ |
D | manifest.stub | 4 Specification-Title: ICU for Java Doc Tools 7 Implementation-Title: ICU for Java Doc Tools 14 Specification-Title: ICU for Java Resource Index Generator 17 Implementation-Title: ICU for Java Resource Index Generator
|
/external/tensorflow/tensorflow/tools/lib_package/ |
D | README.md | 27 ## Java library 29 The TensorFlow [Java 31 consists of a native library (`libtensorflow_jni.so`) and a Java archive (JAR). 46 - The Java archive at: 48 - The Java archive for Java sources at:
|
/external/grpc-grpc-java/examples/android/ |
D | README.md | 1 gRPC Hello World Example (Android Java) 6 - [Java gRPC](https://github.com/grpc/grpc-java) 10 - [gRPC Java Android Quick Start Guide](https://grpc.io/docs/quickstart/android.html) 17 1. (Only for non-released versions) Install gRPC Java
|
/external/xz-java/ |
D | NEWS | 2 XZ for Java release notes 7 * Fix a binary compatibility regression: XZ for Java 1.7 binaries 8 in the Maven Central require Java 9 which is too new. XZ for 9 Java 1.8 binaries require Java 5. (XZ for Java 1.6 and older 10 binaries require Java 1.4.)
|
/external/markdown/tests/misc/ |
D | japanese.txt | 7 …ミング言語 Python は初心者から専門家まで幅広いユーザ層を獲得している。利用目的は汎用で、方向性としてはJavaに近い。ただし、最初からネットワーク利用をメインとして考えられているJavaよ… 15 …の構文はPythonに慣れたユーザからは称賛をもって受け入れられているが、他の言語のユーザからは批判も多い。このほかにも、大きすぎる実行ファイルや、Javaに比べて遅い処理速度などが欠点として指摘…
|
/external/protobuf/docs/ |
D | third_party.md | 51 * Java: https://github.com/google/protobuf (Google-official implementation) 52 * Java/Android: https://github.com/square/wire 53 * Java ME: http://code.google.com/p/protobuf-javame/ 54 * Java ME: http://swingme.sourceforge.net/encode.shtml 55 * Java ME: http://code.google.com/p/protobuf-j2me/ 108 * http://code.google.com/p/protobuf-socket-rpc/ (Java, Python) 109 * http://code.google.com/p/proto-streamer/ (Java) 112 * http://code.google.com/p/protobuf-mina-rpc/ (Python client, Java server) 114 * http://code.google.com/p/cxf-protobuf/ (Java) 116 * http://code.google.com/p/protobuf-rpc-pro/ (Java) [all …]
|
/external/antlr/runtime/Perl5/docs/ |
D | design.pod | 12 primary target language is Java. This port tries to mimic this implementation 18 Java is built on two basic concepts: Objects and Exceptions. If there's a 27 The Java package C<org.antlr.runtime> maps to the Perl 5 package 32 Each Java class maps to a Perl 5 class with the same name. 41 Here's a list of Java types and how they should map to Perl.
|
/external/webrtc/sdk/android/ |
D | README | 1 This directory holds a Java implementation of the webrtc::PeerConnection API, as 2 well as the JNI glue C++ code that lets the Java implementation reuse the C++ 5 To build the Java API and related tests, make sure you have a WebRTC checkout 18 To use the Java API, start by looking at the public interface of
|
/external/oss-fuzz/docs/getting-started/new-project-guide/ |
D | jvm_lang.md | 3 title: Integrating a Java/JVM project 10 # Integrating a Java/JVM project 17 The process of integrating a project written in Java or any other language 18 running on the Java Virtual Machine (JVM) with OSS-Fuzz is very similar to the 25 Java fuzzing in OSS-Fuzz depends on 39 as an example of a simple Java-only fuzzing project. Additional examples, 40 including one for a Java project with native dependencies, are part of the 54 specified explicitly even for pure Java projects. 79 In the simplest case, every fuzzer consists of a single Java file with a 98 Java-only project with single-file fuzz targets as described above: [all …]
|
/external/bcc/tools/ |
D | javathreads_example.txt | 4 uthreads traces thread creation events in Java or raw (C) pthreads, and prints 5 details about the newly created thread. For Java threads, the thread name is 9 For example, trace all Java thread creation events: 19 ID, when available. The accuracy of this information depends on the Java 57 ./uthreads -l java 185 # trace Java threads in process 185
|
12345678910>>...51