Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #12855

Re: Javascript directly calling the Google App Engine

From BGB <cr88192@hotmail.com>
Newsgroups comp.lang.javascript
Subject Re: Javascript directly calling the Google App Engine
Date 2012-03-17 10:24 -0700
Organization albasani.net
Message-ID <jk2hfv$o37$1@news.albasani.net> (permalink)
References <7577204.4705.1331535049931.JavaMail.geo-discussion-forums@ynnk21> <2455587.J1nglo7zMT@PointedEars.de> <2UVL3KD5nyXPFw5i@J.A830F0FF37FB96852AD08924D9443D28E23ED5CD> <jjtmib$h9n$1@news.albasani.net> <1609776.kdTlGXAFRq@PointedEars.de>

Show all headers | View raw


On 3/17/2012 4:05 AM, Thomas 'PointedEars' Lahn wrote:
> BGB wrote:
>
>> On 3/13/2012 4:05 AM, John G Harris wrote:
>>> On Tue, 13 Mar 2012 at 00:03:13, in comp.lang.javascript, Thomas
>>> 'PointedEars' Lahn wrote:
>>>     <snip>
>>>> There is no "javascript", that is a common misconception.
>>>     <snip>
>>>
>>> Is there anyone else who agrees with Thomas ?
>>
>> technically, one can argue that the "real" language in question is
>> ECMAScript, which comes in several varieties:
>> JavaScript;
>> JScript;
>> ActionScript;
>> ...
>
> One would be wrong, then.  ECMAScript is a standard for object-oriented
> programming languages, precisely scripting languages ("programming
> language[s] that [are] used to manipulate, customise, and automate the
> facilities of an existing system") [1].  JavaScript, JScript, and
> ActionScript are some of the different implementations of that standard that
> (sometimes conformingly) differ from the standard and from each another;
> they are ECMAScript implementations.
>
> It is important to make that distinction, not least because it matters which
> implementation is being talked about, as it is the host environment that
> defines the implementation that is used.  In this case, the ECMAScript
> implementation that was being referred to with "javascript" was probably,
> but not necessarily, Google V8 3.7.12.12 or later in Google Chrome
> 17.0.963.78 or later [2].
>

fair enough.

however, ECMAScript tends to differ a little more between 
implementations than do some other languages (such as C or Java), and is 
a little fuzzier around the edges.

the term "varieties" was used in the sense that although they each have 
the core language in common, but may introduce a number of specific 
quirks (whether or not the variety is the same as a particular 
implementation was considered a secondary matter, but may be fairly 
relevant).


> See also<http://PointedEars.de/es-matrix>  (a rather extensive update to
> include the results of my current work is coming in a few months from now).
>

interesting...


and in my case there is the matter of how to classify my own 
language/implementation/variant/whatever, which is used primarily for 
application scripting purposes. going by the table, it would appear that 
it probably is an implementation (what features are problematic seem 
on-par with other implementations).

however, it doesn't mean it is necessarily interchangeable with other 
implementations though, as the way I use both the language and VM are 
fairly dependent on implementation-specific details (particularly 
regarding the C FFI and similar).


>
> PointedEars
> ___________
> [1] Ecma International (June 2011). Standard ECMA-262. ECMAScript
>      Language Specification. 5.1 Edition.
>      <http://www.ecma-international.org/publications/files/ECMA-
>       ST/Ecma-262.pdf>  (accessed on 2012-03-17).
> [2]<http://code.google.com/p/v8/source/browse/trunk/ChangeLog>

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Javascript directly calling the Google App Engine R Hall <richkhall@gmail.com> - 2012-03-11 23:50 -0700
  Re: Javascript directly calling the Google App Engine "Evertjan." <exjxw.hannivoort@interxnl.net> - 2012-03-12 07:59 +0000
  Re: Javascript directly calling the Google App Engine Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-03-13 00:03 +0100
    Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-13 11:05 +0000
      Re: Javascript directly calling the Google App Engine Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2012-03-13 12:37 +0100
        Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-14 16:24 +0000
          Re: Javascript directly calling the Google App Engine Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2012-03-16 01:55 +0100
      Re: Javascript directly calling the Google App Engine Gene Wirchenko <genew@ocis.net> - 2012-03-13 09:03 -0700
        Re: Javascript directly calling the Google App Engine David Mark <dmark.cinsoft@gmail.com> - 2012-03-13 10:53 -0700
          Re: Javascript directly calling the Google App Engine Gene Wirchenko <genew@ocis.net> - 2012-03-13 12:36 -0700
        Re: Javascript directly calling the Google App Engine Scott Sauyet <scott.sauyet@gmail.com> - 2012-03-13 19:07 -0700
          Re: Javascript directly calling the Google App Engine Gene Wirchenko <genew@ocis.net> - 2012-03-13 22:43 -0700
            Re: Javascript directly calling the Google App Engine Scott Sauyet <scott.sauyet@gmail.com> - 2012-03-16 06:09 -0700
              Re: Javascript directly calling the Google App Engine Gene Wirchenko <genew@ocis.net> - 2012-03-16 12:53 -0700
              Re: Javascript directly calling the Google App Engine David Mark <dmark.cinsoft@gmail.com> - 2012-03-16 13:30 -0700
                Re: Javascript directly calling the Google App Engine Gene Wirchenko <genew@ocis.net> - 2012-03-16 15:42 -0700
                Re: Javascript directly calling the Google App Engine David Mark <dmark.cinsoft@gmail.com> - 2012-03-16 17:32 -0700
          Re: Javascript directly calling the Google App Engine David Mark <dmark.cinsoft@gmail.com> - 2012-03-14 14:04 -0700
            Re: Javascript directly calling the Google App Engine Eric Bednarz <bednarz@fahr-zur-hoelle.org> - 2012-03-16 01:40 +0100
      Re: Javascript directly calling the Google App Engine BGB <cr88192@hotmail.com> - 2012-03-15 14:20 -0700
        Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-16 17:28 +0000
          Re: Javascript directly calling the Google App Engine BGB <cr88192@hotmail.com> - 2012-03-16 10:53 -0700
            Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-17 17:00 +0000
        Re: Javascript directly calling the Google App Engine Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-03-17 12:05 +0100
          Re: Javascript directly calling the Google App Engine BGB <cr88192@hotmail.com> - 2012-03-17 10:24 -0700
      Re: Javascript directly calling the Google App Engine Matt McDonald <matt@fortybelow.ca> - 2012-03-16 19:39 -0600
        Re: Javascript directly calling the Google App Engine David Mark <dmark.cinsoft@gmail.com> - 2012-03-16 18:54 -0700
        Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-17 16:53 +0000
          Re: Javascript directly calling the Google App Engine Matt McDonald <matt@fortybelow.ca> - 2012-03-17 13:10 -0600
            Re: Javascript directly calling the Google App Engine John G Harris <john@nospam.demon.co.uk> - 2012-03-18 13:06 +0000

csiph-web