| /packages/apps/VoiceDialer/src/com/android/voicedialer/ |
| PhoneTypeChoiceRecognizerEngine.java | 61 String semantic = mSrec.getResult(result, Recognizer.KEY_MEANING); local
62 String msg = "conf=" + conf + " lit=" + literal + " sem=" + semantic;
71 String semantic = mSrec.getResult(0, Recognizer.KEY_MEANING); local
72 String msg = "conf=" + conf + " lit=" + literal + " sem=" + semantic;
76 if (("H".equalsIgnoreCase(semantic)) ||
77 ("M".equalsIgnoreCase(semantic)) ||
78 ("W".equalsIgnoreCase(semantic)) ||
79 ("O".equalsIgnoreCase(semantic)) ||
80 ("R".equalsIgnoreCase(semantic)) ||
81 ("X".equalsIgnoreCase(semantic))) {
[all...] |
| CommandRecognizerEngine.java | 338 // the "semantic" string, which is easy to overflow. So now,
341 // for literal and semantic.
960 String semantic = mSrec.getResult(result, Recognizer.KEY_MEANING); local
[all...] |
| /external/antlr/antlr-3.4/runtime/ActionScript/project/src/org/antlr/runtime/ |
| DFA.as | 5 * Any state that has a semantic predicate edge is special; those states
|
| /external/ceres-solver/docs/ |
| faq.tex | 21 In most problems there is a natural parameter block structure, as there is a semantic meaning associated with groups of scalars -- mean vector of a distribution, color of a pixel etc. To group two scalar variables, ask yourself if residual blocks will always use these two variables together. If the answer is yes, then the two variables belong to the same parameter block.
|
| /external/clang/lib/CodeGen/ |
| CGExpr.cpp | 3224 const Expr *semantic = *i; local
[all...] |
| CGObjC.cpp | 2457 const Expr *semantic = *i; local
[all...] |
| /external/clang/lib/Sema/ |
| SemaPseudoObject.cpp | 1 //===--- SemaPseudoObject.cpp - Semantic Analysis for Pseudo-Objects ------===//
10 // This file implements semantic analysis for expressions involving
170 /// Add a normal semantic expression.
171 void addSemanticExpr(Expr *semantic) {
172 Semantics.push_back(semantic);
175 /// Add the 'result' semantic expression.
312 // and set the new semantic
319 // Otherwise, it must already be one of our semantic expressions;
[all...] |
| /external/antlr/antlr-3.4/runtime/Ruby/lib/antlr3/ |
| tree.rb | 72 Trees (ASTs), tree structures that reflect the high-level syntactic and semantic
[all...] |
| /external/libvorbis/doc/ |
| 08-residue.tex | 12 hybrids as mixed by channel coupling. The exact semantic content of
|
| 01-introduction.tex | 315 specification, it need not be a literal semantic implementation.
|
| /external/clang/include/clang/AST/ |
| Expr.h | 712 /// by semantic analysis for function calls, object constructions, etc. in
[all...] |
| /external/antlr/antlr-3.4/runtime/Delphi/Sources/Antlr3.Runtime/ |
| Antlr.Runtime.pas | [all...] |
