HomeSort by relevance Sort by last modified time
    Searched full:production (Results 376 - 400 of 750) sorted by null

<<11121314151617181920>>

  /external/bison/src/
scan-code.l 626 _("symbol not found in production before $%d: %.*s");
633 _("symbol not found in production: %.*s");
  /external/chromium_org/chrome/browser/
chrome_browser_application_mac.mm 180 // production.
190 // to be very uncommon in production, because of the OOM killer.
  /external/chromium_org/chromeos/dbus/
power_manager_client.cc 43 // The PowerManagerClient implementation used in production.
635 // Origin thread (i.e. the UI thread in production).
    [all...]
dbus_thread_manager.cc 257 // The DBusThreadManager implementation used in production.
debug_daemon_client.cc 41 // The DebugDaemonClient implementation used in production.
  /external/chromium_org/content/browser/web_contents/
web_contents_view_aura_browsertest.cc 590 // a production build. It only passed prior to this revision
593 // how this test should work that mimics production code a bit
  /external/chromium_org/v8/src/
preparser.cc 396 // * It is a Syntax Error if the code that matches this production is not
423 // * It is a Syntax Error if the code that matches this production is not
  /external/clang/lib/Parse/
ParseInit.cpp 107 /// ParseInitializerWithPotentialDesignator - Parse the 'initializer' production
305 // an assignment-expression production.
  /external/icu/icu4c/source/samples/ustring/
ustring.cpp 86 // Production code should be aware of what encoding is required,
281 * For production code where many strings are titlecased it would be more efficient
  /frameworks/base/docs/html/google/play/billing/
billing_testing.jd 254 overrides the usual Google Play production system. When you send an In-app Billing request for a
255 reserved product ID, the quality of service will not be comparable to the production
  /frameworks/base/docs/html/tools/testing/
activity_testing.jd 107 helps you control the test environment and isolate it from production systems. You can
133 a production system.
  /external/mdnsresponder/mDNSShared/
DebugServices.h 397 debugging without being penalized for production builds.
414 debugging without being penalized for production builds.
546 Code inside check() statements is not compiled into production builds.
577 Code inside check_string() statements is not compiled into production builds.
609 Code inside check_noerr() statements is not compiled into production builds.
644 Code inside check_noerr_string() statements is not compiled into production builds.
676 Code inside check_translated_errno() statements is not compiled into production builds.
    [all...]
  /external/bison/po/
ru.po 662 msgid "symbol not found in production before $%d: %.*s"
667 msgid "symbol not found in production: %.*s"
    [all...]
fr.po 679 msgid "symbol not found in production before $%d: %.*s"
680 msgstr "symbole pas trouvé en production avant $%d: %.*s"
684 msgid "symbol not found in production: %.*s"
685 msgstr "symbole pas trouvé en production: %.*s"
    [all...]
  /frameworks/base/docs/html/google/gcm/
ccs.jd 83 functionality (with non-production users), you should instead connect to
91 avoid upstream messages from production traffic being sent over test connections.</p>
    [all...]
  /device/generic/goldfish/opengl/tests/gles_android_wrapper/
egl.cpp 19 // This code meant to be used for testing purposes only. It is not production
  /device/lge/mako/nfc/
libnfc-brcm.conf 114 # should be removed for production.
  /device/samsung/manta/nfc/
libnfc-brcm.conf 114 # should be removed for production.
  /docs/source.android.com/src/devices/
audio_debugging.jd 45 done debugging; the tee sink should not be left enabled in production builds.
  /external/antlr/antlr-3.4/tool/src/main/resources/org/antlr/tool/templates/messages/languages/
en.stg 181 "reference $<arg> is ambiguous; rule <arg> is enclosing rule and referenced in the production (assuming enclosing rule)"
  /external/apache-xml/src/main/java/org/apache/xml/serializer/
Encodings.java 197 * whose name does not match the EncName production of the XML Recommendation
  /external/bison/
TODO 306 that returns the tree node for the production. Easy. But I also needed
  /external/chromium_org/chrome/browser/extensions/
extension_system_impl.cc 166 // so also consider extensions with the default (production) update url
  /external/chromium_org/chrome/browser/sync_file_system/drive_backend/
metadata_database.h 141 // The entry point of the MetadataDatabase for production code.
  /external/chromium_org/chrome/common/extensions/docs/server2/test_data/github_file_system/test_owner/repo/commits/
HEAD 124 "patch": "@@ -1,6 +1,6 @@\n ## Overview of Chrome In App Payments API\n \n-You can use the Chrome In App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome Wallet App (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n+You can use the Chrome In-App Payments API (Chrome IAP API) to sell digital and virtual goods within a Chrome App. When you use the Chrome IAP API, the Chrome In-App Payments Service (embedded in Chrome) communicates with the Google Wallet servers and handles all the required checkout details so your app does not have to process any financial transactions. The actual integration work to enable in app payments is similar to using the [Google Wallet digital goods API](https://developers.google.com/commerce/wallet/digital/docs/) for websites except that the Chrome IAP API requires you to embed a piece of JavaScript ([buy.js](https://raw.github.com/GoogleChrome/chrome-app-samples/master/in-app-payments/buy.js)) within your app to trigger the payment flow.\n \n ## Sample app\n Here?s a sample app that calls into the Chrome IAP API and provides options to trigger payments via the sandbox server as well as the production server:"

Completed in 229 milliseconds

<<11121314151617181920>>