2.4 Feature List

[AnEmortalKid]

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

• Documentation Updates Update documentation for 2.4.0 #86
• Anonymous function support Anonymous function support #87
• Deprecate truedoge mode Deprecate "true doge" mode #85
  • Also deprecate from plugins
• throw/try/catch/finally throw / try / catch / finally #76 consider keywords
• typeof and instanceof typeof & instanceof #75
• commonJS module.exports keyword Need a feature for commonJS module.exports #73
• debugger support Doge debugger statement #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. wow. such ideas #35
• possible ambiguity reduction: is conflict #45 is => same and maybe also
• Class/Extends support Class 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]

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

[AnEmortalKid]

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]

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]

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

[AnEmortalKid]

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]

Leads seems like it would imply the other direction

[AnEmortalKid]

Ah, I didn't see it that way:

Polygon <- Shape, maybe xtends ?

[Griffork]

How about grows?

…

On Sat., 9 Jun. 2018, 14:12 Jan Monterrubio, ***@***.***> wrote: Ah, I didn't see it that way: Polygon <- Shape, maybe xtends ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#114 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADfwTunpOdf-yJR9DGXcK70f2uPCD9LRks5t60tIgaJpZM4P0yAu> .

[Purpzie]

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]

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]

Fixed #73 with #131

[AnEmortalKid]

Property accessors in #35 fixed with #192 #197

[AnEmortalKid]

=== -> same
== -> like

based on:

JavaScript has both strict and type–converting comparisons. A strict comparison (e.g., ===) is only true if the operands are of the same type and the contents match. The more commonly-used abstract comparison (e.g. ==) converts the operands to the same type before making the comparison. For relational abstract comparisons (e.g., <=), the operands are first converted to primitives, then to the same type, before comparison.

[AnEmortalKid]

Both do/while and try/catch/finally require some better capturing of state. The state tracking mechanisms for 2.4.0 are limited, and at this point the re-write would handle these better.

[AnEmortalKid]

https://www.npmjs.com/package/grunt-dogescript/v/2.4.0
https://www.npmjs.com/package/dogescript-loader/v/2.4.0
https://www.npmjs.com/package/require-doge/v/2.4.0

This completes this issue :) 🥳