Comments on: JScript. Dynamic languages’ forgotten cousin.

By: Chui’s counterpoint » Blog Archive » Prototype-based Languages and Design-Tension

Sat, 11 Mar 2006 11:32:52 +0000

[...] Luckily for JavaScript, implementations such as Rhino and JScript leverage off the OO libraries of JVM and CLR respectively. I think these implementations have great potential, since they benefit from the OO libraries (objects whose behaviour are easier to figure out), but offer the advantage of prototypes, where behavior can be modified without having to subclass. [...]

By: J Wynia

J Wynia — Wed, 11 May 2005 01:45:22 +0000

Though not entirely current anymore, I can’t help but respond.

import System
import System.Windows.Forms
import System.IO

All valid JScript.NET imports.

Anthony, have you even LOOKED at JScript.NET? JScript.NET uses all of the .NET assemblies, any COM object you like, dynamically eval other JScript code (in some cases) and otherwise generally participate in .NET in *exactly the same ways* as C#. JScript.NET is compiled, just like C. It can be used to build DLL assemblies which in turn can be used in the languages like Python and C via COM wrappers.

Exactly which “Packages” can’t JScript.NET handle.

By: Anthony

Anthony — Tue, 15 Mar 2005 13:32:03 +0000

One answer Packages. Languages that excel allow programmers to use the work of others. Take C and python.. the #include and the import statement are the corner of their success. Now what was that statement in JScript?? Oh I can’t remember..