How "non-standard" is _defineGetter?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Ken Tilton

    How "non-standard" is _defineGetter?

    Total JS noob here, but porting my hairy Common Lisp Cells (dataflow)
    package -- long intro on my blog:

    [We may as well get this out of the way, an explanation of my pet project Cells, the kind of thing I'll be sitting in a rocking chair twenty...


    ....so I am getting into some fun stuff straight-away.

    I am happy to see _defineGetter_/Setter_ here:

    The Object type represents one of JavaScript's data types. It is used to store various keyed collections and more complex entities. Objects can be created using the Object() constructor or the object initializer / literal syntax.


    Those are crucial to the transparency of my hack, but there it mentions
    they are "Non-standard". I would like Cells/js to be portable -- is this
    something to be concerned about?

    kenny

    --
    Grossly unfair, unreliable, biased, and pretty much delusional rants and ravings on Lisp from a simple working application programmer.



    "I've never read the rulebook. My job is to catch the ball."
    -- Catcher Josh Bard after making a great catch on a foul ball
    he might have let drop and then sliding into the dugout, which
    by the rules allowed the runners to advance one base costing his
    pitcher a possible shutout because there was a runner
    on third base.

    "My sig is longer than most of my articles."
    -- Kenny Tilton
  • Joost Diepenmaat

    #2
    Re: How "non-standard" is _defineGetter?

    Ken Tilton <kennytilton@op tonline.netwrit es:
    Total JS noob here, but porting my hairy Common Lisp Cells (dataflow)
    package -- long intro on my blog:
    >
    [We may as well get this out of the way, an explanation of my pet project Cells, the kind of thing I'll be sitting in a rocking chair twenty...

    >
    ...so I am getting into some fun stuff straight-away.
    >
    I am happy to see _defineGetter_/Setter_ here:
    >
    The Object type represents one of JavaScript's data types. It is used to store various keyed collections and more complex entities. Objects can be created using the Object() constructor or the object initializer / literal syntax.

    >
    Those are crucial to the transparency of my hack, but there it
    mentions they are "Non-standard". I would like Cells/js to be portable
    -- is this something to be concerned about?
    Yup. It's *completely* useless for general purposes. Which (as usual)
    means it doesn't work in MS Internet Explorer, which has something like
    90% of the user base.

    In general, for language level stuff like this, if it isn't mentioned in
    ecma-262, you can more or less bet on it not being available in a
    significant portion of browsers (and IE doesn't even support all of
    it correctly, but AFAICT nothing really significant).

    ECMAScript® 2025 language specification, 16th edition - ECMAScript is a programming language based on several technologies like JavaScript.



    --
    Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/

    Comment

    • Ken Tilton

      #3
      Re: How &quot;non-standard&quot; is _defineGetter?



      Joost Diepenmaat wrote:
      Ken Tilton <kennytilton@op tonline.netwrit es:
      >
      >
      >>Total JS noob here, but porting my hairy Common Lisp Cells (dataflow)
      >>package -- long intro on my blog:
      >>
      > http://smuglispweeny.blogspot.com/20...manifesto.html
      >>
      >>...so I am getting into some fun stuff straight-away.
      >>
      >>I am happy to see _defineGetter_/Setter_ here:
      >>
      >>http://developer.mozilla.org/en/docs...Objects:Object
      >>
      >>Those are crucial to the transparency of my hack, but there it
      >>mentions they are "Non-standard". I would like Cells/js to be portable
      >>-- is this something to be concerned about?
      >
      >
      Yup. It's *completely* useless for general purposes. Which (as usual)
      means it doesn't work in MS Internet Explorer, which has something like
      90% of the user base.
      >
      In general, for language level stuff like this, if it isn't mentioned in
      ecma-262, you can more or less bet on it not being available in a
      significant portion of browsers (and IE doesn't even support all of
      it correctly, but AFAICT nothing really significant).
      >
      ECMAScript® 2025 language specification, 16th edition - ECMAScript is a programming language based on several technologies like JavaScript.

      >
      >
      Joost! Long time no. :) Thx, I was having no luck finding a nice solid
      JS reference.

      And thanks for heading me off form a dead end on the get/set deal.

      kenny

      --
      Grossly unfair, unreliable, biased, and pretty much delusional rants and ravings on Lisp from a simple working application programmer.



      "I've never read the rulebook. My job is to catch the ball."
      -- Catcher Josh Bard after making a great catch on a foul ball
      and then sliding into the dugout, which by the rules allowed the
      runners to advance one base costing his pitcher a possible shutout
      because there was a runner on third base.

      "My sig is longer than most of my articles."
      -- Kenny Tilton

      Comment

      Working...