Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.4 Feature List #114

Open
AnEmortalKid opened this issue Oct 11, 2017 · 12 comments

Comments

Projects
None yet
4 participants
@AnEmortalKid
Copy link
Member

commented Oct 11, 2017

Placeholder to link all the other currently open issues planned for 2.4 that existed pre-revive.

  • Documentation Updates #86
  • Anonymous function support #87
  • Deprecate truedoge mode #85
    • Also deprecate from plugins
  • throw/try/catch/finally #76 consider keywords
  • typeof and instanceof #75
  • commonJS module.exports keyword #73
  • debugger support #74 (replace with pawse)
  • array levl 1 => array[1] , ary is pack -> ary = [] , pares -> obj definition. Also from or something to do obj.prop, maybe gimme or giv obj gimme prop obj giv prop. #35
  • possible ambiguity reduction: #45 is => same and maybe also
  • Class/Extends support #126
  • do/while support
  • Expression support in IF statements (i.e very Math dose random bigger 3)
  • Info on syntax errors (line / token) instead of just throwing them.
  • break keyword
@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Oct 15, 2017

#87 already existed (verified in #104 since we had to backtrack).

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Mar 19, 2018

For #45 , I think i'd like to rename the comparison is to same:


very foo is 'wow'
very bar is 'wow'
rly foo same bar
console dose loge with 'wowser'
but
console dose loge with 'sad'
wow

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Mar 22, 2018

Looking at ECMA 5 support: (keywords) https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Lexical_grammar

for class, extends, super:

classy Polygon very Shape
  such constructor much name
    sooper with name
  wow
wow

or:

so Polygon very Shape
  such constructor much name
    sooper with name
  wow
wow

so might lead to confusion. it could be so classy Polygon...

=>

class Polygon extends Shape {

constructor(name) {
  super(name);
}

}
@vpzomtrrfrt

This comment has been minimized.

Copy link
Member

commented Mar 22, 2018

super should probably still use plz. Since so is already used for imports, I'd lean toward classy between those two options

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Jun 9, 2018

Since very is already variable declaration (and our parser is a bit messy), what about:

classy Polygon leads Shape
  such constructor much name
    plz sooper with name
  wow
wow

so:

classy -> class
leads -> extends, I was trying to make a pun on leash, like classy blah drags blah or classy blah leash blah
sooper -> super

@vpzomtrrfrt

This comment has been minimized.

Copy link
Member

commented Jun 9, 2018

Leads seems like it would imply the other direction

@AnEmortalKid AnEmortalKid added this to the 2.4.0 milestone Jun 9, 2018

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Jun 9, 2018

Ah, I didn't see it that way:

Polygon <- Shape, maybe xtends ?

@Griffork

This comment has been minimized.

Copy link

commented Jun 9, 2018

@Purpzie

This comment has been minimized.

Copy link

commented Sep 20, 2018

I would definitely prefer giv over gimme to be honest, just since it's shorter. Perhaps it could support both, though, if people can't decide.

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Oct 7, 2018

I would definitely prefer giv over gimme to be honest, just since it's shorter. Perhaps it could support both, though, if people can't decide.

Let's go with giv first and adding gimme later should be fairly easy

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Nov 14, 2018

Fixed #73 with #131

@AnEmortalKid AnEmortalKid pinned this issue Dec 14, 2018

@AnEmortalKid

This comment has been minimized.

Copy link
Member Author

commented Mar 5, 2019

Property accessors in #35 fixed with #192 #197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.