Women in Technology

Hear us Roar

  VBScript or Perl?
Subject:   Why not JScript?
Date:   2003-11-23 07:29:16
From:   anonymous2
Response to: Why not JScript?

In a WSH environment JScript support is limitted. Prototype-based inheritance just doesn't work, so this renders JScript useless. I haven't worked with WSH extensive, so I might be wrong.
Full Threads Oldest First

Showing messages 1 through 2 of 2.

  • Why not JScript?
    2003-12-31 02:19:07  anonymous2 [View]

    Um, I don't see how JScript is useless? VBScript (and VB for that matter) only supports Object-Based programming, and through COM you cannot derive objects from one another anyhow. So, I don't see how lack of inheritence makes a difference when it comes to interfacing with COM libraries such as WMI, ADSI, Office, CDO, DAO, ADO, etc.

    FYI, The newer JScript.NET (ECMAScript ver 4) supports true inheritence, but that's a different topic...

    - Joaquin M.
  • Why not JScript?
    2003-12-01 13:44:39  anonymous2 [View]

    You are wrong. JScript support in WSH is not limited. Prototype-based inheritance does work.

    For WSH I tend to use .wsf files and mix JScript and Perl. I like using JScript's exception handling especially when using COM objects. If I need to spawn a process I prefer to use Perl to open a pipe instead of using the WshScriptExec object.