Javascript > JavaScript

app/BUILD.anvil

@@ -7,7 +7,7 @@ __author__ = 'benvanik@google.com (Ben Vanik)'
 
 
 # ------------------------------------------------------------------------------
-# Javascript
+# JavaScript
 # ------------------------------------------------------------------------------
 
 file_set(

bin/instrument.js

@@ -47,7 +47,7 @@ var processScript = ctx['wtfi']['process'];
 
 
 /**
- * Transforms Javascript source code into a instrumented version.
+ * Transforms JavaScript source code into a instrumented version.
  * @param {number} moduleId Module ID, [0-126].
  * @param {string} url URL of the source code.
  * @param {string} sourceCode Source code.
@@ -544,7 +544,7 @@ function main(argv) {
 
 
 main(optimist
-    .usage('Instrument Javascript for tracing.\nUsage: $0 source.js [source.instrumented.js]\n       $0 --server')
+    .usage('Instrument JavaScript for tracing.\nUsage: $0 source.js [source.instrumented.js]\n       $0 --server')
     .options('s', {
       alias: 'server',
       type: 'boolean',

docs/call_tracing.md

@@ -15,7 +15,7 @@ So the call tracing feature is implemented entirely differently. It is **not for
 timing** - you will not be able to get function times from this! What you will
 be seeing in the user interface is counts, based on the mode you're running in.
 
-The `wtf-instrument` command line tool runs over your Javascript to produce
+The `wtf-instrument` command line tool runs over your JavaScript to produce
 an instrumented file that can be run in the browser. Unlike the normal
 instrumentation that normal WTF does, this process performs code transformation
 and results in a different kind of file: `.wtf-calls`.
@@ -71,7 +71,7 @@ npm install -g tracing-framework
 
 ## Manual Instrumentation
 
-If you have a Javascript file you'd like to instrument the easiest way to get
+If you have a JavaScript file you'd like to instrument the easiest way to get
 started is by using the `wtf-instrument` tool included in the npm package
 (aka `./bin/instrument.js` in the repo).
 
@@ -88,13 +88,13 @@ version. That's it! See below for how to actually use the instrumented page.
 
 Caveats:
 
-* Only one Javascript file on a page can be instrumented this way right now. If
+* Only one JavaScript file on a page can be instrumented this way right now. If
 you need more use the proxy below.
 
 ## Automatic Instrumentation
 
 By running a tiny proxy server and using a Chrome extension it's possible to
-automatically instrument all Javascript sources on a page automatically.
+automatically instrument all JavaScript sources on a page automatically.
 
 Flow:
 
@@ -127,7 +127,7 @@ page is fully loaded you can disable the extension.
 
 ## Capturing Call Traces
 
-Once you've instrumented your Javascript with one of the above methods, you can
+Once you've instrumented your JavaScript with one of the above methods, you can
 capture your data.
 
 TODO: future versions will have a fancy UI, maybe.

docs/options.md

@@ -97,7 +97,7 @@ of events to include in the stream or the fidelity of the events added.
 #### wtf.trace.provider.chromeDebug
 
 Set `wtf.trace.provider.chromeDebug` to 1+ to enable the events. This will
-use a variety of means to attempt to gather Javascript runtime events, such as
+use a variety of means to attempt to gather JavaScript runtime events, such as
 garbage collections, JIT activity, etc. This functionality relies on the
 injector extension or custom builds of Chromium. It introduces some overhead,
 such as an additional 0.1ms per XHR open/send.

shims/wtf-trace-closure.js

@@ -211,14 +211,14 @@ WTF.data.EventFlag = {
 WTF.data.ZoneType = {
   /**
    * Primary script context.
-   * Usually just user Javascript scopes. This is the default scope created for
+   * Usually just user JavaScript scopes. This is the default scope created for
    * all traces.
    */
   SCRIPT: 'script',
 
   /**
    * Native script context.
-   * Native runtime scopes, such as the C++ calls above the Javascript.
+   * Native runtime scopes, such as the C++ calls above the JavaScript.
    */
   NATIVE_SCRIPT: 'native_script',
 
@@ -551,7 +551,7 @@ WTF.trace.timeStamp = WTF.PRESENT ?
 /**
  * Begins an async time range.
  * This tracks time outside of normal scope flow control, and should be limited
- * to only those events that span frames or Javascript ticks.
+ * to only those events that span frames or JavaScript ticks.
  * If you're trying to track call flow instead use {@see #traceMethods}.
  *
  * A limited number of active timers will be displayed in the UI. Do not abuse

shims/wtf-trace-disabled.js

@@ -8,7 +8,7 @@
 /**
  * @fileoverview Web Tracing Framework shim, hardcoded to disabled.
  * Use this file to allow a page to use the 'WTF' namespace safely but in
- * a disabled form. Javascript engines will be pretty smart about the WTF calls
+ * a disabled form. JavaScript engines will be pretty smart about the WTF calls
  * and add very little overhead.
  *
  * Original source: https://www.github.com/google/tracing-framework/

shims/wtf-trace.js

@@ -211,14 +211,14 @@ WTF.data.EventFlag = {
 WTF.data.ZoneType = {
   /**
    * Primary script context.
-   * Usually just user Javascript scopes. This is the default scope created for
+   * Usually just user JavaScript scopes. This is the default scope created for
    * all traces.
    */
   SCRIPT: 'script',
 
   /**
    * Native script context.
-   * Native runtime scopes, such as the C++ calls above the Javascript.
+   * Native runtime scopes, such as the C++ calls above the JavaScript.
    */
   NATIVE_SCRIPT: 'native_script',
 
@@ -551,7 +551,7 @@ WTF.trace.timeStamp = WTF.PRESENT ?
 /**
  * Begins an async time range.
  * This tracks time outside of normal scope flow control, and should be limited
- * to only those events that span frames or Javascript ticks.
+ * to only those events that span frames or JavaScript ticks.
  * If you're trying to track call flow instead use {@see #traceMethods}.
  *
  * A limited number of active timers will be displayed in the UI. Do not abuse

src/wtf/data/variable.js

@@ -30,15 +30,15 @@ wtf.data.VariableFlag = {
  * Variable.
  *
  * @param {string} name A machine-friendly name used to uniquely identify
- *     the variable. It should be a valid Javascript literal (no spaces/etc).
+ *     the variable. It should be a valid JavaScript literal (no spaces/etc).
  * @param {string} typeName Variable type name used in signatures.
  * @param {number=} opt_flags Bitmask of {@see wtf.data.VariableFlag} values.
  * @constructor
  */
 wtf.data.Variable = function(name, typeName, opt_flags) {
   /**
    * Machine-friendly name used to uniquely identify the variable. It should be
-   * a valid Javascript literal (no spaces/etc).
+   * a valid JavaScript literal (no spaces/etc).
    * @type {string}
    */
   this.name = name;

src/wtf/data/zonetype.js

@@ -22,14 +22,14 @@ goog.provide('wtf.data.ZoneType');
 wtf.data.ZoneType = {
   /**
    * Primary script context.
-   * Usually just user Javascript scopes. This is the default scope created for
+   * Usually just user JavaScript scopes. This is the default scope created for
    * all traces.
    */
   SCRIPT: 'script',
 
   /**
    * Native script context.
-   * Native runtime scopes, such as the C++ calls above the Javascript.
+   * Native runtime scopes, such as the C++ calls above the JavaScript.
    */
   NATIVE_SCRIPT: 'native_script',
 

src/wtf/db/eventtype.js

@@ -25,7 +25,7 @@ goog.require('wtf.db.EventTypeBuilder');
  * be generated to efficiently read or write the events.
  *
  * @param {string} name A machine-friendly name used to uniquely identify the
- *     event. It should be a valid Javascript literal (no spaces/etc).
+ *     event. It should be a valid JavaScript literal (no spaces/etc).
  * @param {wtf.data.EventClass} eventClass Event class.
  * @param {number} flags A bitmask of {@see wtf.data.EventFlag}.
  * @param {!Array.<!wtf.data.Variable>} args Additional arguments encoded
@@ -42,7 +42,7 @@ wtf.db.EventType = function(name, eventClass, flags, args) {
 
   /**
    * A machine-friendly name used to uniquely identify the event. It should be a
-   * valid Javascript literal (no spaces/etc).
+   * valid JavaScript literal (no spaces/etc).
    * @type {string}
    */
   this.name = name;

src/wtf/io/io.js

@@ -101,7 +101,7 @@ goog.asserts.assert(wtf.io.HAS_TYPED_ARRAYS);
 
 /**
  * Creates a byte array.
- * This will either be a Uint8Array (if supported) or a zeroed Javascript
+ * This will either be a Uint8Array (if supported) or a zeroed JavaScript
  * Array.
  * @param {number} size Size, in bytes.
  * @return {!wtf.io.ByteArray} The new array.

src/wtf/math/mersennetwister.js

@@ -6,7 +6,7 @@
  */
 
 /**
- * @fileoverview A Javascript port of Merseene Twister algorithm.
+ * @fileoverview A JavaScript port of Merseene Twister algorithm.
  * Adapted from https://gist.github.com/banksean/300494
  * by Sean McCullough (banksean@gmail.com).
  *

src/wtf/trace/builtinevents.js

@@ -6,7 +6,7 @@
  */
 
 /**
- * @fileoverview Built-in Javascript event definitions.
+ * @fileoverview Built-in JavaScript event definitions.
  *
  * @author benvanik@google.com (Ben Vanik)
  */

src/wtf/trace/eventtype.js

@@ -25,7 +25,7 @@ goog.require('goog.reflect');
  * be generated to efficiently read or write the events.
  *
  * @param {string} name A machine-friendly name used to uniquely identify the
- *     event. It should be a valid Javascript literal (no spaces/etc).
+ *     event. It should be a valid JavaScript literal (no spaces/etc).
  * @param {wtf.data.EventClass} eventClass Event class.
  * @param {number} flags A bitmask of {@see wtf.data.EventFlag}.
  * @param {Array.<!wtf.data.Variable>=} opt_args Additional arguments encoded
@@ -35,7 +35,7 @@ goog.require('goog.reflect');
 wtf.trace.EventType = function(name, eventClass, flags, opt_args) {
   /**
    * A machine-friendly name used to uniquely identify the event. It should be a
-   * valid Javascript literal (no spaces/etc).
+   * valid JavaScript literal (no spaces/etc).
    * @type {string}
    */
   this.name = name;

src/wtf/trace/providers/consoleprovider.js

@@ -6,7 +6,7 @@
  */
 
 /**
- * @fileoverview Console Javascript event provider.
+ * @fileoverview Console JavaScript event provider.
  *
  * @author benvanik@google.com (Ben Vanik)
  */

src/wtf/trace/providers/replayprovider.js

@@ -6,7 +6,7 @@
  */
 
 /**
- * @fileoverview Replay Javascript event provider.
+ * @fileoverview Replay JavaScript event provider.
  *
  * @author benvanik@google.com (Ben Vanik)
  */

src/wtf/trace/providers/timingprovider.js

@@ -6,7 +6,7 @@
  */
 
 /**
- * @fileoverview Timing Javascript event provider.
+ * @fileoverview Timing JavaScript event provider.
  *
  * @author benvanik@google.com (Ben Vanik)
  */

src/wtf/trace/trace.js

@@ -687,7 +687,7 @@ wtf.trace.nextTimeRange_ = 0;
 /**
  * Begins an async time range.
  * This tracks time outside of normal scope flow control, and should be limited
- * to only those events that span frames or Javascript ticks.
+ * to only those events that span frames or JavaScript ticks.
  * If you're trying to track call flow instead use {@see #traceMethods}.
  *
  * A limited number of active timers will be displayed in the UI. Do not abuse