| JS++ | |
| Paradigm: | Multi-paradigm Imperative, structured, object-oriented, functional, generic |
| Family: | ECMAScript |
| Designer: | Roger Poon, Anton Rapetov |
| Developer: | Onux |
| Latest Release Version: | 0.10.0 |
| Typing: | Gradual, static, dynamic |
| Scope: | lexical |
| License: | BSD |
| File Ext: | .jspp, .js++, .jpp |
| File Formats: | --> |
| Influenced By: | C, C++, C#, Java, JavaScript |
JS++ is a programming language for web development that extends JavaScript with a sound type system. It includes imperative, object-oriented, functional, and generic programming features. It is free and open-source software released under a BSD license.
JS++ first appeared on October 8, 2011.[1] [2] [3] The modern implementation was announced at DeveloperWeek 2016[4] and released on May 31, 2016.[5] [6] [7] [8] The language is designed by Roger Poon and Anton Rapetov.
Since JS++ is a superset of JavaScript, declaring data types for variables is optional. However, when types are declared, the types are enforced at both compile time and runtime.
Type annotations in JS++ use the traditional C/C++ syntax:
Notably, this differs from TypeScript and ActionScript, which use a more verbose style:
The type system in JS++ is sound for ECMAScript and DOM API corner cases, including host objects, dynamic key-value pairs, Comet, JScript conditional compilation, dynamic return types, ActiveX, ECMAScript for XML, web browser garbage collector and cyclic reference counting bugs, conditional logic, and other edge and corner cases.[9] [10] This differs from other JavaScript supersets where types are optional and discarded at runtime via type erasure, such as in TypeScript.[11] [12]
JS++ can use JavaScript libraries using the one-line external statement as in the following example from the homepage of JS++:
class Example
While classes in JavaScript (ECMAScript 6) are syntactic sugar for prototypes under the hood,[13] JS++ classes resemble the classes found in classical programming languages such as C++, Java, and C# in terms of memory layout, performance, and semantics. "Classes" are a static concept, and they cannot be altered at runtime (during program execution) as is the case for JavaScript, Smalltalk, Lisp, and TypeScript, which rely on prototypes.[14] For example, private methods are private at both compile time and runtime, and external JavaScript objects cannot access private JS++ fields or methods—even if a reference to a JS++ object is obtained from JavaScript.
The following source code illustrates object-oriented sorting in JS++ using the IComparablecompare method below:
Employee zig = new Employee("Zig", "Ziglar");Employee john = new Employee("John", "Smith");Employee abe = new Employee("Abe", "Lincoln");
Employee[] employees = [zig, john, abe ];employees.sort;Console.log(employees.join(", "));
// Output:// Abe Lincoln, John Smith, Zig Ziglar
Thus, in the code above, the custom sorting logic provided is:
Likewise, to call the sort:
For printing the sorted results:
JS++ provides encapsulation by default. In the following example, the fields x and y are private by default, even if no access modifier is specified. The methods getX and getY are public by default. This enables a more concise class definition syntax, as illustrated in the Point class below:[16]
An out-of-bounds access usually occurs with arrays and other containers. For example, when we access the 100th element of a 3-element array, we have an out-of-bounds access:
In Java and C#, this can result in an exception and program termination. In C, this can result in buffer overflows or segmentation faults. C++ has varying semantics, such as default initialization, exceptions, segmentation faults, or buffer overflows.[17] [18]
JS++ can efficiently analyze and prevent out-of-bounds errors at compile time.[19] [20] [21]
JavaScript has the notion of null and undefined values, where null means a value is present but it's an empty value, and undefined means there isn't a value there at all. JS++ extends this intuition further to differentiate between empty values and out-of-bounds accesses.
Consider the following code, with a nullable int type represented with int?:
null)
While nullable types can represent an out-of-bounds access, it falls apart when the array might contain nullable values as illustrated above. Instead, JS++ introduces an additional concept in addition to null values: undefined values. Recall that JS++ extends the JavaScript notion that null means a value is present but is an empty value, while an undefined value means a value does not exist at all. JS++ uses the concept of "a value does not exist at all" to mean an out-of-bounds access has occurred, and this concept is known in JS++ as "existent types."
Therefore, the previous example can be amended. The existent type int+ means "int or out of bounds" and int?+ means "int, null, or out of bounds":
int?[] b = [1, null ];int?+ value2 = b[2];if (value2
Intuitively, this means existent types cannot be used as the underlying type for array elements. JS++ enforces this at compile time:
style="color: silver; background: black;">[ ERROR ] JSPPE5204: Existent type `int+' cannot be used as the element type for arrays
Instead of following every conditional branch or virtual method call path, which would result in path explosion and exponential compile times, existent types have essentially the same compile-time analysis cost as int, bool, and other primitive types. Consequently, compile times have been shown to be unaffected (±1-2ms) by the introduction of existent types. Since existent types are used for all array and container types in JS++ (such as hash maps, Stack<T>, and Queue<T>), JS++ containers are thus guaranteed to not have out-of-bounds errors.
In JS++, undefined is a value that cannot be changed. In JavaScript (ECMAScript 3), undefined is a mutable property of the global object, resulting in circumstances where "undefined" can be "defined."[22] Thus, existent types would not have been possible in pure JavaScript, as arrays can contain elements with the undefined value, undefined can be defined, or other edge and corner cases that are prevented in JS++.[23]
Also, in comparison to Java and early object-oriented languages such as Eiffel,[24] [25] JS++ does not default initialize objects to null. Instead, the compiler enforces initialization by the programmer:
Car car;
style="color: silver; background: black;">[ ERROR ] JSPPE6000: Variable `car' is not initialized at line 3 char 4
Therefore, since existent types are deeply embedded into the language, JS++ can guarantee that out-of-bounds errors never occur.[26]
The concept of existent types can be extended outside of containers. For example, in MySQL, columns can be nullable.[27] [28] If the row does not exist for a specified condition (e.g. WHERE clause), the undefined value can be returned. However, if the row does exist but the value at the column is empty, a null value can be returned instead. This can simplify the code and interfaces to the data access layer.
JS++ provides 8-bit, 16-bit, 32-bit, and 64-bit integer types as well as floating point types:
float f = 0.5; // single-precision floating pointdouble d = 0.5; // double-precision floating point
From the project homepage:
// But, if you do, this next variable will always remain an 'unsigned int' - even at runtime.// You'll never see NaN ("Not a Number") runtime errors again.// This variable is 'unsigned' so it's also guaranteed to never be negative.unsigned int pageHeight = $(document).height;
All variables in JS++ are block-scoped, including the JavaScript var statement.[29] [30] [31] Thus, there is no need for two different variable declaration keywords with different scoping rules, such as var and let co-existing simultaneously in JavaScript (ECMAScript 6).
The JS++ compiler is available for Windows, macOS, and Linux. It is a source-to-source compiler which emits JavaScript source code as an intermediate representation.
The compiler is developed with C/C++, and the developers claim there are "fewer than 10 open bug reports in the core compiler" after 3.5 years of engineering and 400,000 lines of code.[32]
JS++ integrates with various code editors including Visual Studio Code, Atom, and Sublime Text.[33] [34] [35]
JS++ can be integrated with third-party build tools like Webpack.[36]
| Version number | Release date | Changes | |
|---|---|---|---|
| 0.01 | Alpha version, initial release | ||
| 0.011 | Alpha version | ||
| 0.012 | Alpha version | ||
| 0.013 | Alpha version | ||
| 0.014.1 | Alpha version | ||
| 0.4.1 | Beta version, array and callback types, character literals, integral suffixes, removed ECMAScript ASI | ||
| 0.4.2 | Modules, function overloading, dead code elimination, editor integrations | ||
| 0.4.2.1 | Bug fixes | ||
| 0.4.2.2 | Source map debugging | ||
| 0.4.2.4 | Support for Mac OS X, C-style casts, callback and array conversions | ||
| 0.5.0 | Classes | ||
| 0.5.1 | 'foreach' loops | ||
| 0.5.2 | BSD License, Interfaces, Abstract Classes, Virtual Methods, Auto-boxing | ||
| 0.7.0 | All ECMAScript 3 features via Array | ||
| 0.8.0 | Generic programming, Dictionary | ||
| 0.8.1 | auto, catch-all clauses, standard library modules for handling time, bug fixes | ||
| 0.8.4 | New string functions, advanced generics, bug fixes, standard library expansion | ||
| 0.8.5 | Bug fixes | ||
| 0.8.10 | Faster compile times, stacks, queues, Unicode, Base64, generic default constraint rules | ||
| 0.9.0 | Efficient compile time out-of-bounds error analysis | ||
| 0.9.1 | Bug fixes | ||
| 0.9.2 | Final (immutable) variables and default to 64-bit for macOS Catalina |
