What's the history of the unused keyword package, is it from Java?
Been thinking about this lately, could an external module be called a package?
package/file.js
package something {
export class foo {}
}
package other {
export class foo {}
export module bar {
export class foo {}
What use cases does this solve?
From: es-discuss [mailto:es-discuss-boun...@mozilla.org] On Behalf Of Jonathan
Bond-Caron
Sent: Friday, April 11, 2014 16:56
To: es-discuss
Subject: package keyword reserved?
What's the history of the unused keyword package, is it from Java?
Been thinking about
Jonathan Bond-Caron wrote:
What’s the history of the unused keyword “package”, is it from Java?
In 1995, I reserved all the Java (JDK1.0 era) reserved identifiers.
ES1 kept them, but ES5 cut way back, yet kept 'package' among others as
reserved in strict code. No one had a championed
What use cases does this solve for JavaScript, not TypeScript?
-Original Message-
From: Jonathan Bond-Caron [mailto:jbo...@gdesolutions.com]
Sent: Friday, April 11, 2014 17:44
To: Domenic Denicola; es-discuss
Subject: RE: package keyword reserved?
On Fri Apr 11 05:25 PM, Domenic
On Fri Apr 11 05:52 PM, Domenic Denicola wrote:
What use cases does this solve for JavaScript, not TypeScript?
Not sure, benefit comes down to subjective preference. Keeps the single
'module' per file pattern from node.js
Is it safe to use the 'package' keyword then, no proposals for using
On Fri, Apr 11, 2014 at 6:23 PM, Jonathan Bond-Caron
jbo...@gdesolutions.com wrote:
On Fri Apr 11 05:52 PM, Domenic Denicola wrote:
What use cases does this solve for JavaScript, not TypeScript?
Not sure, benefit comes down to subjective preference. Keeps the single
'module' per file
Jonathan Bond-Caron wrote:
Is it safe to use the 'package' keyword then, no proposals for using it?
You mean for some other language compiled to JS to use 'package'? If so,
then no: it's unsafe, explicitly so. The 'package' identifier is a
strict future reserved word. Steer clear, the TC39
7 matches
Mail list logo
