kotovalexarian-likes-github
/
jashkenas--coffeescript
mirror of https://github.com/jashkenas/coffeescript.git
1
0
Fork 0
Code Releases Activity
jashkenas--coffeescript/lib/coffee-script/parser.js

721 lines
77 KiB
JavaScript
Raw Normal View History

Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
/* parser generated by jison 0.4.15 */
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
/*
Returns a Parser object of the following structure:
Parser: {
yy: {}
}
Parser.prototype: {
yy: {},
trace: function(),
symbols_: {associative list: name ==> number},
terminals_: {associative list: number ==> name},
productions_: [...],
performAction: function anonymous(yytext, yyleng, yylineno, yy, yystate, $$, _$),
table: [...],
defaultActions: {...},
parseError: function(str, hash),
parse: function(input),
lexer: {
EOF: 1,
parseError: function(str, hash),
setInput: function(input),
input: function(),
unput: function(str),
more: function(),
less: function(n),
pastInput: function(),
upcomingInput: function(),
showPosition: function(),
test_match: function(regex_match_array, rule_index),
next: function(),
lex: function(),
begin: function(condition),
popState: function(),
_currentRules: function(),
topState: function(),
pushState: function(condition),
options: {
ranges: boolean (optional: true ==> token location info will include a .range[] member)
flex: boolean (optional: true ==> flex-like lexing behaviour where the rules are tested exhaustively to find the longest match)
backtrack_lexer: boolean (optional: true ==> lexer regexes are tested in order and for each matching regex the action code is invoked; the lexer terminates the scan when a token is returned by the action code)
},
performAction: function(yy, yy_, $avoiding_name_collisions, YY_START),
rules: [...],
conditions: {associative list: name ==> set},
}
}
token location info (@$, _$, etc.): {
first_line: n,
last_line: n,
first_column: n,
last_column: n,
range: [start_number, end_number] (where the numbers are indexes into the input string, regular zero-based)
}
the parseError function receives a 'hash' object with these members for lexer and parser errors: {
text: (matched text)
token: (the produced terminal token, if any)
line: (yylineno)
}
while parser (grammar) errors will also provide these members, i.e. parser errors deliver a superset of attributes: {
loc: (yylloc)
expected: (string describing the set of expected tokens)
recoverable: (boolean: TRUE when the parser has a error recovery rule available for this particular error)
}
*/
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
var parser = (function(){
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
var o=function(k,v,o,l){for(o=o||{},l=k.length;l--;o[k[l]]=v);return o},$V0=[1,20],$V1=[1,75],$V2=[1,71],$V3=[1,76],$V4=[1,77],$V5=[1,73],$V6=[1,74],$V7=[1,50],$V8=[1,52],$V9=[1,53],$Va=[1,54],$Vb=[1,55],$Vc=[1,45],$Vd=[1,46],$Ve=[1,27],$Vf=[1,60],$Vg=[1,61],$Vh=[1,70],$Vi=[1,43],$Vj=[1,26],$Vk=[1,58],$Vl=[1,59],$Vm=[1,57],$Vn=[1,38],$Vo=[1,44],$Vp=[1,56],$Vq=[1,65],$Vr=[1,66],$Vs=[1,67],$Vt=[1,68],$Vu=[1,42],$Vv=[1,64],$Vw=[1,29],$Vx=[1,30],$Vy=[1,31],$Vz=[1,32],$VA=[1,33],$VB=[1,34],$VC=[1,35],$VD=[1,78],$VE=[1,6,26,34,108],$VF=[1,88],$VG=[1,81],$VH=[1,80],$VI=[1,79],$VJ=[1,82],$VK=[1,83],$VL=[1,84],$VM=[1,85],$VN=[1,86],$VO=[1,87],$VP=[1,91],$VQ=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$VR=[1,97],$VS=[1,98],$VT=[1,99],$VU=[1,100],$VV=[1,102],$VW=[1,103],$VX=[1,96],$VY=[2,112],$VZ=[1,6,25,26,34,55,60,63,72,73,74,75,77,79,80,84,90,91,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$V_=[2,79],$V$=[1,108],$V01=[2,58],$V11=[1,112],$V21=[1,117],$V31=[1,118],$V41=[1,120],$V51=[1,6,25,26,34,46,55,60,63,72,73,74,75,77,79,80,84,90,91,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$V61=[2,76],$V71=[1,6,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$V81=[1,155],$V91=[1,157],$Va1=[1,152],$Vb1=[1,6,25,26,34,46,55,60,63,72,73,74,75,77,79,80,84,86,90,91,92,97,99,108,110,111,112,116,117,132,135,136,139,140,141,142,143,144,145,146,147,148],$Vc1=[2,95],$Vd1=[1,6,25,26,34,49,55,60,63,72,73,74,75,77,79,80,84,90,91,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$Ve1=[1,6,25,26,34,46,49,55,60,63,72,73,74,75,77,79,80,84,86,90,91,92,97,99,108,110,111,112,116,117,123,124,132,135,136,139,140,141,142,143,144,145,146,147,148],$Vf1=[1,206],$Vg1=[1,205],$Vh1=[1,6,25,26,34,38,55,60,63,72,73,74,75,77,79,80,84,90,91,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$Vi1=[2,56],$Vj1=[1,216],$Vk1=[6,25,26,55,60],$Vl1=[6,25,26,46,55,60,63],$Vm1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,132,135,136,142,144,145,146,147],$Vn1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,132],$Vo1=[72,73,74,75,77,80,90,91],$Vp1=[1,235],$Vq1=[2,133],$Vr1=[1,6,25,26,34,46,55,60,63,72,73,74,75,77,79,80,84,90,91,92,97,99,108,110,111,112,116,117,123,124,132,135,136,141,142,143,144,145,146,147],$Vs1=[1,244],$Vt1=[6,25,26,60,92,97],$Vu1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,117,132],$Vv1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,111,117,132],$Vw1=[123,124],$Vx1=[60,123,124],$Vy1=[1,255],$Vz1=[6,25,26,60,84],$VA1=[6,25,26,49,60,84],$VB1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,132,135,136,144,145,146,147],$VC1=[11,28,30,32,33,36,37,40,41,42,43,44,51,52,53,57,58,79,82,85,89,94,95,96,102,106,107,110,112,114,116,125,131,133,134,135,136,137,139,140],$VD1=[2,122],$VE1=[6,25,26],$VF1=[2,57],$VG1=[1,268],$VH1=[1,269],$VI1=[1,6,25,26,34,55,60,63,79,84,92,97,99,104,105,108,110,111,112,116,117,127,129,132,135,136,141,142,143,144,145,146,147],$VJ1=[26,127,129],$VK1=[1,6,26,34,55,60,63,79,84,92,97,99,108,111,117,132],$VL1=[2,71],$VM1=[1,291],$VN1=[1,292],$VO1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,111,112,116,117,127,132,135,136,141,142,143,144,145,146,147],$VP1=[1,6,25,26,34,55,60,63,79,84,92,97,99,108,110,112,116,117,132],$VQ1=[1,303],$VR1=[1,304],$VS1=[6,25,26,60],$VT1=[1,6,25,26,34,55,60,63,79,84,92,97,99,104,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],$VU1=[25,60];
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
var parser = {trace: function trace() { },
yy: {},
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
symbols_: {"error":2,"Root":3,"Body":4,"Line":5,"TERMINATOR":6,"Expression":7,"Statement":8,"Return":9,"Comment":10,"STATEMENT":11,"Value":12,"Invocation":13,"Code":14,"Operation":15,"Assign":16,"If":17,"Try":18,"While":19,"For":20,"Switch":21,"Class":22,"Throw":23,"Block":24,"INDENT":25,"OUTDENT":26,"Identifier":27,"IDENTIFIER":28,"AlphaNumeric":29,"NUMBER":30,"String":31,"STRING":32,"STRING_START":33,"STRING_END":34,"Regex":35,"REGEX":36,"REGEX_START":37,"REGEX_END":38,"Literal":39,"JS":40,"DEBUGGER":41,"UNDEFINED":42,"NULL":43,"BOOL":44,"Assignable":45,"=":46,"AssignObj":47,"ObjAssignable":48,":":49,"ThisProperty":50,"RETURN":51,"HERECOMMENT":52,"PARAM_START":53,"ParamList":54,"PARAM_END":55,"FuncGlyph":56,"->":57,"=>":58,"OptComma":59,",":60,"Param":61,"ParamVar":62,"...":63,"Array":64,"Object":65,"Splat":66,"SimpleAssignable":67,"Accessor":68,"Parenthetical":69,"Range":70,"This":71,".":72,"?.":73,"::":74,"?::":75,"Index":76,"INDEX_START":77,"IndexValue":78,"INDEX_END":79,"INDEX_SOAK":80,"Slice":81,"{":82,"AssignList":83,"}":84,"CLASS":85,"EXTENDS":86,"OptFuncExist":87,"Arguments":88,"SUPER":89,"FUNC_EXIST":90,"CALL_START":91,"CALL_END":92,"ArgList":93,"THIS":94,"@":95,"[":96,"]":97,"RangeDots":98,"..":99,"Arg":100,"SimpleArgs":101,"TRY":102,"Catch":103,"FINALLY":104,"CATCH":105,"THROW":106,"(":107,")":108,"WhileSource":109,"WHILE":110,"WHEN":111,"UNTIL":112,"Loop":113,"LOOP":114,"ForBody":115,"FOR":116,"BY":117,"ForStart":118,"ForSource":119,"ForVariables":120,"OWN":121,"ForValue":122,"FORIN":123,"FOROF":124,"SWITCH":125,"Whens":126,"ELSE":127,"When":128,"LEADING_WHEN":129,"IfBlock":130,"IF":131,"POST_IF":132,"UNARY":133,"UNARY_MATH":134,"-":135,"+":136,"YIELD":137,"FROM":138,"--":139,"++":140,"?":141,"MATH":142,"**":143,"SHIFT":144,"COMPARE":145,"LOGIC":146,"RELATION":147,"COMPOUND_ASSIGN":148,"$accept":0,"$end":1},
terminals_: {2:"error",6:"TERMINATOR",11:"STATEMENT",25:"INDENT",26:"OUTDENT",28:"IDENTIFIER",30:"NUMBER",32:"STRING",33:"STRING_START",34:"STRING_END",36:"REGEX",37:"REGEX_START",38:"REGEX_END",40:"JS",41:"DEBUGGER",42:"UNDEFINED",43:"NULL",44:"BOOL",46:"=",49:":",51:"RETURN",52:"HERECOMMENT",53:"PARAM_START",55:"PARAM_END",57:"->",58:"=>",60:",",63:"...",72:".",73:"?.",74:"::",75:"?::",77:"INDEX_START",79:"INDEX_END",80:"INDEX_SOAK",82:"{",84:"}",85:"CLASS",86:"EXTENDS",89:"SUPER",90:"FUNC_EXIST",91:"CALL_START",92:"CALL_END",94:"THIS",95:"@",96:"[",97:"]",99:"..",102:"TRY",104:"FINALLY",105:"CATCH",106:"THROW",107:"(",108:")",110:"WHILE",111:"WHEN",112:"UNTIL",114:"LOOP",116:"FOR",117:"BY",121:"OWN",123:"FORIN",124:"FOROF",125:"SWITCH",127:"ELSE",129:"LEADING_WHEN",131:"IF",132:"POST_IF",133:"UNARY",134:"UNARY_MATH",135:"-",136:"+",137:"YIELD",138:"FROM",139:"--",140:"++",141:"?",142:"MATH",143:"**",144:"SHIFT",145:"COMPARE",146:"LOGIC",147:"RELATION",148:"COMPOUND_ASSIGN"},
productions_: [0,[3,0],[3,1],[4,1],[4,3],[4,2],[5,1],[5,1],[8,1],[8,1],[8,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[7,1],[24,2],[24,3],[27,1],[29,1],[29,1],[31,1],[31,3],[35,1],[35,3],[39,1],[39,1],[39,1],[39,1],[39,1],[39,1],[39,1],[16,3],[16,4],[16,5],[47,1],[47,3],[47,5],[47,1],[48,1],[48,1],[48,1],[9,2],[9,1],[10,1],[14,5],[14,2],[56,1],[56,1],[59,0],[59,1],[54,0],[54,1],[54,3],[54,4],[54,6],[61,1],[61,2],[61,3],[61,1],[62,1],[62,1],[62,1],[62,1],[66,2],[67,1],[67,2],[67,2],[67,1],[45,1],[45,1],[45,1],[12,1],[12,1],[12,1],[12,1],[12,1],[68,2],[68,2],[68,2],[68,2],[68,1],[68,1],[76,3],[76,2],[78,1],[78,1],[65,4],[83,0],[83,1],[83,3],[83,4],[83,6],[22,1],[22,2],[22,3],[22,4],[22,2],[22,3],[22,4],[22,5],[13,3],[13,3],[13,1],[13,2],[87,0],[87,1],[88,2],[88,4],[71,1],[71,1],[50,2],[64,2],[64,4],[98,1],[98,1],[70,5],[81,3],[81,2],[81,2],[81,1],[93,1],[93,3],[93,4],[93,4],[93,6],[100,1],[100,1],[100,1],[101,1],[101,3],[18,2],[18,3],[18,4],[18,5],[103,3],[103,3],[103,2],[23,2],[69,3],[69,5],[109,2],[109,4],[109,2],[109,4],[19,2],[19,2],[19,2],[19,1],[113,2],[113,2],[20,2],[20,2],[20,2],[115,2],[115,4],[115,2],[118,2],[118,3],[122,1],[122,1],[122,1],[122,1],[120,1],[120,3],[119,2],[119,2],[119,4],[119,4],[119,4],[119,6],[119,6],[21,5],[21,7],[21,4],[21,6],[126,1],[126,2],[128,3],[128,4],[130,3],[130,5],[17,1],[17,3],[17,3],[17,3],[15,2],[15,2],[15,2],[15,2],[15,2],[15,2],[15,3],[15,2],[15,2],[15,2],[15,2],[15,2],[15,3],[15,3],[15,3],[15,3],[15,3],[15,3],[15,3],[15,3],[15,3],[15,5],[15,4],[15,3]],
Fix #3671: Allow step in optimized range comprehensions Allow the `by c` part in `for [a..b] by c then`. Continue disallowing a `when d` part, since it makes no sense having a guard that isn't given access to anything that changes on every iteration.
2015-01-10 01:31:56 +00:00
performAction: function anonymous(yytext, yyleng, yylineno, yy, yystate /* action[1] */, $$ /* vstack */, _$ /* lstack */) {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
/* this == yyval */
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
var $0 = $$.length - 1;
switch (yystate) {
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 1:
return this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Block);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 2:
return this.$ = $$[$0];
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 3:
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(yy.Block.wrap([$$[$0]]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 4:
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])($$[$0-2].push($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 5:
this.$ = $$[$0-1];
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 6: case 7: case 8: case 9: case 11: case 12: case 13: case 14: case 15: case 16: case 17: case 18: case 19: case 20: case 21: case 22: case 27: case 32: case 34: case 45: case 46: case 47: case 48: case 56: case 57: case 67: case 68: case 69: case 70: case 75: case 76: case 79: case 83: case 89: case 133: case 134: case 136: case 166: case 167: case 183: case 189:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = $$[$0];
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 10: case 25: case 26: case 28: case 30: case 33: case 35:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Literal($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
case 23:
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Block);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 24: case 31: case 90:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])($$[$0-1]);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 29: case 146:
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Parens($$[$0-1]));
break;
case 36:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Undefined);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 37:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Null);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 38:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Bool($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 39:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Assign($$[$0-2], $$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 40:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Assign($$[$0-3], $$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 41:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Assign($$[$0-4], $$[$0-1]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 42: case 72: case 77: case 78: case 80: case 81: case 82: case 168: case 169:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Value($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 43:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Assign(yy.addLocationDataFn(_$[$0-2])(new yy.Value($$[$0-2])), $$[$0], 'object'));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 44:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Assign(yy.addLocationDataFn(_$[$0-4])(new yy.Value($$[$0-4])), $$[$0-1], 'object'));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 49:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Return($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 50:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Return);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 51:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Comment($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 52:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Code($$[$0-3], $$[$0], $$[$0-1]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 53:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Code([], $$[$0], $$[$0-1]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 54:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])('func');
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 55:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])('boundfunc');
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 58: case 95:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])([]);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 59: case 96: case 128: case 170:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])([$$[$0]]);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 60: case 97: case 129:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])($$[$0-2].concat($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 61: case 98: case 130:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])($$[$0-3].concat($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 62: case 99: case 132:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-5], _$[$0])($$[$0-5].concat($$[$0-2]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 63:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Param($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 64:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Param($$[$0-1], null, true));
making debugger an expression.
2011-11-25 13:35:20 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 65:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Param($$[$0-2], $$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 66: case 135:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Expansion);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 71:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Splat($$[$0-1]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 73:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])($$[$0-1].add($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 74:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Value($$[$0-1], [].concat($$[$0])));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 84:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Access($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 85:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Access($$[$0], 'soak'));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 86:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])([yy.addLocationDataFn(_$[$0-1])(new yy.Access(new yy.Literal('prototype'))), yy.addLocationDataFn(_$[$0])(new yy.Access($$[$0]))]);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 87:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])([yy.addLocationDataFn(_$[$0-1])(new yy.Access(new yy.Literal('prototype'), 'soak')), yy.addLocationDataFn(_$[$0])(new yy.Access($$[$0]))]);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 88:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Access(new yy.Literal('prototype')));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 91:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(yy.extend($$[$0], {
nodes: @soakNode -> @soak
2010-10-25 13:31:52 +00:00
soak: true
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
adding passed-through block comments back to the grammar/lexer/rewriter/nodes ... thanks, Trevor Burnham.
2010-07-02 01:26:33 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 92:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Index($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 93:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Slice($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 94:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Obj($$[$0-2], $$[$0-3].generated));
removing an unused rule in Root.
2010-11-13 23:13:09 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 100:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Class);
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 101:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Class(null, null, $$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 102:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Class(null, $$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 103:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Class(null, $$[$0-1], $$[$0]));
grammar: removed a remnant of Slice
2010-10-23 20:35:35 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 104:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Class($$[$0]));
Minor modifications to the grammar to allow a single trailing comma for function call arguments, array literal and object literals. Adjusted tests accordingly
2010-03-26 15:44:25 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 105:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Class($$[$0-1], null, $$[$0]));
removing the <- bind operator from CoffeeScript...
2010-06-12 15:00:56 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 106:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Class($$[$0-2], $$[$0]));
Minor modifications to the grammar to allow a single trailing comma for function call arguments, array literal and object literals. Adjusted tests accordingly
2010-03-26 15:44:25 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 107:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Class($$[$0-3], $$[$0-1], $$[$0]));
Minor modifications to the grammar to allow a single trailing comma for function call arguments, array literal and object literals. Adjusted tests accordingly
2010-03-26 15:44:25 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 108: case 109:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Call($$[$0-2], $$[$0], $$[$0-1]));
Minor modifications to the grammar to allow a single trailing comma for function call arguments, array literal and object literals. Adjusted tests accordingly
2010-03-26 15:44:25 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 110:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Call('super', [new yy.Splat(new yy.Literal('arguments'))]));
Fixed a small bug that happened when having a trailing comma in multiline array and object literals
2010-03-26 18:11:34 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 111:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Call('super', $$[$0]));
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 112:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(false);
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 113:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(true);
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 114:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])([]);
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 115: case 131:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])($$[$0-2]);
Addressing some assignment issues.
2010-03-28 17:06:16 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 116: case 117:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Value(new yy.Literal('this')));
Addressing some assignment issues.
2010-03-28 17:06:16 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 118:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Value(yy.addLocationDataFn(_$[$0-1])(new yy.Literal('this')), [yy.addLocationDataFn(_$[$0])(new yy.Access($$[$0]))], 'this'));
Addressing some assignment issues.
2010-03-28 17:06:16 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 119:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Arr([]));
Restricted class and extends values to simple assignments.
2010-03-28 17:14:35 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 120:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Arr($$[$0-2]));
adding class methods to class definition syntax, using '@'
2010-03-30 01:43:12 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 121:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])('inclusive');
first draft of CoffeeScript language extensions.
2010-03-10 04:04:16 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 122:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])('exclusive');
first draft of CoffeeScript language extensions.
2010-03-10 04:04:16 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 123:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Range($$[$0-3], $$[$0-1], $$[$0-2]));
allowing terminator/comment as a block, so that you can have comment-only blocks
2010-03-10 21:18:17 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 124:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Range($$[$0-2], $$[$0], $$[$0-1]));
Added the possibility to end an identifier with '::', refering directly to its prototype.
2010-03-16 21:39:36 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 125:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Range($$[$0-1], null, $$[$0]));
Added the '<-' currying operator, as heavily discussed in #251, along with tests.
2010-03-17 07:11:10 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 126:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Range(null, $$[$0], $$[$0-1]));
Added the '<-' currying operator, as heavily discussed in #251, along with tests.
2010-03-17 07:11:10 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 127:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])(new yy.Range(null, null, $$[$0]));
adding nice support for fancy implicit hashes
2010-07-25 06:52:02 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 137:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])([].concat($$[$0-2], $$[$0]));
adding nice support for fancy implicit hashes
2010-07-25 06:52:02 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 138:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Try($$[$0]));
Adding anonymous class support (gets a temporary variable for a name.) Issue #548
2010-07-28 02:05:55 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 139:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Try($$[$0-1], $$[$0][0], $$[$0][1]));
Disallowing Splats outside of ParamLists and ArgLists ... where they belong. This is in anticipation of the next commit...
2010-08-19 01:27:10 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 140:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Try($$[$0-2], null, null, $$[$0]));
Fixes #1838
2011-12-14 23:31:20 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 141:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Try($$[$0-3], $$[$0-2][0], $$[$0-2][1], $$[$0]));
Issue #621. Added the ability to leave the start and end index off of arrays. list[5..] is now valid CoffeeScript, slicing to the end of the array.
2010-08-19 01:51:44 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 142:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])([$$[$0-1], $$[$0]]);
Added expansion to destructuring
2014-01-24 16:00:34 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 143:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])([yy.addLocationDataFn(_$[$0-1])(new yy.Value($$[$0-1])), $$[$0]]);
Issue #621. Added the ability to leave the start and end index off of arrays. list[5..] is now valid CoffeeScript, slicing to the end of the array.
2010-08-19 01:51:44 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 144:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])([null, $$[$0]]);
Issue #621. Added the ability to leave the start and end index off of arrays. list[5..] is now valid CoffeeScript, slicing to the end of the array.
2010-08-19 01:51:44 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 145:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Throw($$[$0]));
Issue #621. Added the ability to leave the start and end index off of arrays. list[5..] is now valid CoffeeScript, slicing to the end of the array.
2010-08-19 01:51:44 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 147:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Parens($$[$0-2]));
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 148:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.While($$[$0]));
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 149:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.While($$[$0-2], {
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
guard: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 150:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.While($$[$0], {
adding until loops as the inverse of while loops
2010-04-29 02:08:00 +00:00
invert: true
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
adding until loops as the inverse of while loops
2010-04-29 02:08:00 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 151:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.While($$[$0-2], {
adding until loops as the inverse of while loops
2010-04-29 02:08:00 +00:00
invert: true,
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
guard: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
eliminating the IndentedAssignList nonterminal.
2010-04-26 01:22:29 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 152:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])($$[$0-1].addBody($$[$0]));
fixing static class properties that are implicit objects.
2010-09-19 02:25:45 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 153: case 154:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])($$[$0].addBody(yy.addLocationDataFn(_$[$0-1])(yy.Block.wrap([$$[$0-1]]))));
made `catch` optional
2010-10-04 20:53:32 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 155:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0], _$[$0])($$[$0]);
making debugger an expression.
2011-11-25 13:35:20 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 156:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.While(yy.addLocationDataFn(_$[$0-1])(new yy.Literal('true'))).addBody($$[$0]));
Fixes #1838
2011-12-14 23:31:20 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 157:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.While(yy.addLocationDataFn(_$[$0-1])(new yy.Literal('true'))).addBody(yy.addLocationDataFn(_$[$0])(yy.Block.wrap([$$[$0]]))));
Allowing both end-points of slices to be implicit.
2011-12-21 00:21:26 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 158: case 159:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.For($$[$0-1], $$[$0]));
Closes #971. Existensial slices now supported.
2011-01-22 06:56:14 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 160:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.For($$[$0], $$[$0-1]));
Fixes #2508 -- existential access of the prototype.
2013-03-04 09:07:47 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 161:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])({
Fixes #2508 -- existential access of the prototype.
2013-03-04 09:07:47 +00:00
source: yy.addLocationDataFn(_$[$0])(new yy.Value($$[$0]))
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
allowing Klass::['dynamic-property'] syntax. Issue #392
2010-06-01 02:32:43 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 162:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])({
Fix #3671: Allow step in optimized range comprehensions Allow the `by c` part in `for [a..b] by c then`. Continue disallowing a `when d` part, since it makes no sense having a guard that isn't given access to anything that changes on every iteration.
2015-01-10 01:31:56 +00:00
source: yy.addLocationDataFn(_$[$0-2])(new yy.Value($$[$0-2])),
step: $$[$0]
});
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 163:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])((function () {
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
$$[$0].own = $$[$0-1].own;
Removing 'do', in favor of a trailing ->
2010-12-21 23:54:36 +00:00
$$[$0].name = $$[$0-1][0];
$$[$0].index = $$[$0-1][1];
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
return $$[$0];
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}()));
adding slightly optimized syntax for range comprehensions that could care less about the index variable. Issue #547
2010-07-28 02:38:38 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 164:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])($$[$0]);
adding slightly optimized syntax for range comprehensions that could care less about the index variable. Issue #547
2010-07-28 02:38:38 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 165:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])((function () {
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
$$[$0].own = true;
return $$[$0];
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}()));
fixing static class properties that are implicit objects.
2010-09-19 02:25:45 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 171:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])([$$[$0-2], $$[$0]]);
Fixes #2580 -- Try/Catch is allowed to destructure the error object.
2012-10-23 21:57:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 172:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 173:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0],
first draft of range literals back...
2010-11-20 21:25:22 +00:00
object: true
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
first draft of range literals back...
2010-11-20 21:25:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 174:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0-2],
guard: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 175:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0-2],
guard: $$[$0],
first draft of range literals back...
2010-11-20 21:25:22 +00:00
object: true
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
Removed unprocessed values on a for loop from the grammar.
2010-03-28 18:32:01 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 176:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0-2],
step: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
Removed unprocessed values on a for loop from the grammar.
2010-03-28 18:32:01 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 177:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-5], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0-4],
guard: $$[$0-2],
step: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 178:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-5], _$[$0])({
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
source: $$[$0-4],
step: $$[$0-2],
guard: $$[$0]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
});
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 179:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Switch($$[$0-3], $$[$0-1]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 180:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-6], _$[$0])(new yy.Switch($$[$0-5], $$[$0-3], $$[$0-1]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 181:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Switch(null, $$[$0-1]));
enabling condition-less switches.
2010-05-11 02:57:51 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 182:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-5], _$[$0])(new yy.Switch(null, $$[$0-3], $$[$0-1]));
enabling condition-less switches.
2010-05-11 02:57:51 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 184:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])($$[$0-1].concat($$[$0]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 185:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])([[$$[$0-1], $$[$0]]]);
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 186:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])([[$$[$0-2], $$[$0-1]]]);
Added Statement to the grammar.
2010-04-05 14:26:23 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 187:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.If($$[$0-1], $$[$0], {
Issue #958. Removing UNLESS tokens to make them just inverted IFs.
2010-12-21 03:50:49 +00:00
type: $$[$0-2]
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 188:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])($$[$0-4].addElse(yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.If($$[$0-1], $$[$0], {
Issue #958. Removing UNLESS tokens to make them just inverted IFs.
2010-12-21 03:50:49 +00:00
type: $$[$0-2]
Speed up `updateLocationDataIfMissing`. * Avoid excessive search for missing `locationData` * Fix `locationData` for `ELSE IF`.
2013-06-21 00:47:29 +00:00
}))));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 190:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])($$[$0-2].addElse($$[$0]));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 191: case 192:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.If($$[$0], yy.addLocationDataFn(_$[$0-2])(yy.Block.wrap([$$[$0-2]])), {
Issue #958. Removing UNLESS tokens to make them just inverted IFs.
2010-12-21 03:50:49 +00:00
type: $$[$0-1],
adding complete documentation for the grammar
2010-03-07 16:41:56 +00:00
statement: true
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 193: case 194: case 197: case 198:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op($$[$0-1], $$[$0]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 195:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('-', $$[$0]));
removing an unused rule in Root.
2010-11-13 23:13:09 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 196:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('+', $$[$0]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 199:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Op($$[$0-2].concat($$[$0-1]), $$[$0]));
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 200:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('--', $$[$0]));
being stricter about body-less scoped loops.
2010-12-22 01:28:48 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 201:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('++', $$[$0]));
Fixes #1838
2011-12-14 23:31:20 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 202:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('--', $$[$0-1], null, true));
Allowing both end-points of slices to be implicit.
2011-12-21 00:21:26 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 203:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Op('++', $$[$0-1], null, true));
Fixes #2274 -- allow @variables as loop variables
2012-04-24 16:21:47 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 204:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-1], _$[$0])(new yy.Existence($$[$0-1]));
lexer/parser: split out `null` and `undefined` from `BOOL` token also made explicit AST nodes `Bool`, `Null`, and `Undefined`
2012-05-08 20:11:23 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 205:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Op('+', $$[$0-2], $$[$0]));
removed support for '->*" and '=>*'
2014-09-06 10:55:27 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 206:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Op('-', $$[$0-2], $$[$0]));
lexer/parser: split out `null` and `undefined` from `BOOL` token also made explicit AST nodes `Bool`, `Null`, and `Undefined`
2012-05-08 20:11:23 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 207: case 208: case 209: case 210: case 211:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Op($$[$0-1], $$[$0-2], $$[$0]));
Fixes #2580 -- Try/Catch is allowed to destructure the error object.
2012-10-23 21:57:22 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 212:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])((function () {
rebuilt parser with Jison 0.2.0
2010-12-20 01:04:49 +00:00
if ($$[$0-1].charAt(0) === '!') {
Revert #2599
2013-02-28 13:37:30 +00:00
return new yy.Op($$[$0-1].slice(1), $$[$0-2], $$[$0]).invert();
combination of satyr's three comment patches ... comments are now statements, not expressions...
2010-11-09 04:39:21 +00:00
} else {
Revert #2599
2013-02-28 13:37:30 +00:00
return new yy.Op($$[$0-1], $$[$0-2], $$[$0]);
combination of satyr's three comment patches ... comments are now statements, not expressions...
2010-11-09 04:39:21 +00:00
}
Fix merge problem, and rebuild parser.js
2013-02-22 01:17:06 +00:00
}()));
allowing empty parens.
2010-08-18 01:31:32 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 213:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Assign($$[$0-2], $$[$0], $$[$0-1]));
coco 98271e6: made 'extends' chainable
2010-11-09 05:26:31 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 214:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-4], _$[$0])(new yy.Assign($$[$0-4], $$[$0-1], $$[$0-3]));
Disallowing Splats outside of ParamLists and ArgLists ... where they belong. This is in anticipation of the next commit...
2010-08-19 01:27:10 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 215:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-3], _$[$0])(new yy.Assign($$[$0-3], $$[$0], $$[$0-2]));
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
break;
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
case 216:
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
this.$ = yy.addLocationDataFn(_$[$0-2], _$[$0])(new yy.Extends($$[$0-2], $$[$0]));
Issue #633. 'not instanceof'
2010-08-21 12:56:25 +00:00
break;
Allowing for negative indices in slice literals.
2010-03-21 14:59:41 +00:00
}
},
Fix #3597: Allow interpolations in object keys The following is now allowed: o = a: 1 b: 2 "#{'c'}": 3 "#{'d'}": 4 e: 5 "#{'f'}": 6 g: 7 It compiles to: o = ( obj = { a: 1, b: 2 }, obj["" + 'c'] = 3, obj["" + 'd'] = 4, obj.e = 5, obj["" + 'f'] = 6, obj.g = 7, obj ); - Closes #3039. Empty interpolations in object keys are now _supposed_ to be allowed. - Closes #1131. No need to improve error messages for attempted key interpolation anymore. - Implementing this required fixing the following bug: `("" + a): 1` used to error out on the colon, saying "unexpected colon". But really, it is the attempted object key that is unexpected. Now the error is on the opening parenthesis instead. - However, the above fix broke some error message tests for regexes. The easiest way to fix this was to make a seemingly unrelated change: The error messages for unexpected identifiers, numbers, strings and regexes now say for example 'unexpected string' instead of 'unexpected """some #{really long} string"""'. In other words, the tag _name_ is used instead of the tag _value_. This was way easier to implement, and is more helpful to the user. Using the tag value is good for operators, reserved words and the like, but not for tokens which can contain any text. For example, 'unexpected identifier' is better than 'unexpected expected' (if a variable called 'expected' was used erraneously). - While writing tests for the above point I found a few minor bugs with string locations which have been fixed.
2015-02-07 19:16:59 +00:00
table: [{1:[2,1],3:1,4:2,5:3,7:4,8:5,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,139:$VB,140:$VC},{1:[3]},{1:[2,2],6:$VD},o($VE,[2,3]),o($VE,[2,6],{118:69,109:89,115:90,110:$Vq,112:$Vr,116:$Vt,132:$VF,135:$VG,136:$VH,141:$VI,142:$VJ,143:$VK,144:$VL,145:$VM,146:$VN,147:$VO}),o($VE,[2,7],{118:69,109:92,115:93,110:$Vq,112:$Vr,116:$Vt,132:$VP}),o($VQ,[2,11],{87:94,68:95,76:101,72:$VR,73:$VS,74:$VT,75:$VU,77:$VV,80:$VW,90:$VX,91:$VY}),o($VQ,[2,12],{76:101,87:104,68:105,72:$VR,73:$VS,74:$VT,75:$VU,77:$VV,80:$VW,90:$VX,91:$VY}),o($VQ,[2,13]),o($VQ,[2,14]),o($VQ,[2,15]),o($VQ,[2,16]),o($VQ,[2,17]),o($VQ,[2,18]),o($VQ,[2,19]),o($VQ,[2,20]),o($VQ,[2,21]),o($VQ,[2,22]),o($VQ,[2,8]),o($VQ,[2,9]),o($VQ,[2,10]),o($VZ,$V_,{46:[1,106]}),o($VZ,[2,80]),o($VZ,[2,81]),o($VZ,[2,82]),o($VZ,[2,83]),o([1,6,25,26,34,38,55,60,63,72,73,74,75,77,79,80,84,90,92,97,99,108,110,111,112,116,117,132,135,136,141,142,143,144,145,146,147],[2,110],{88:107,91:$V$}),o([6,25,55,60],$V01,{54:109,61:110,62:111,27:113,50:114,64:115,65:116,28:$V1,63:$V11,82:$Vh,95:$V21,96:$V31}),{24:119,25:$V41},{7:121,8:122,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,139:$VB,140:$VC},{7:123,8:122,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,139:$VB,140:$VC},{7:124,8:122,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,139:$VB,140:$VC},{7:125,8:122,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,139:$VB,140:$VC},{7:127,8:126,9:18,10:19,11:$V0,12:6,13:7,14:8,15:9,16:10,17:11,18:12,19:13,20:14,21:15,22:16,23:17,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39:22,40:$V7,41:$V8,42:$V9,43:$Va,44:$Vb,45:21,50:63,51:$Vc,52:$Vd,53:$Ve,56:28,57:$Vf,58:$Vg,64:47,65:48,67:36,69:23,70:24,71:25,82:$Vh,85:$Vi,89:$Vj,94:$Vk,95:$Vl,96:$Vm,102:$Vn,106:$Vo,107:$Vp,109:39,110:$Vq,112:$Vr,113:40,114:$Vs,115:41,116:$Vt,118:69,125:$Vu,130:37,131:$Vv,133:$Vw,134:$Vx,135:$Vy,136:$Vz,137:$VA,138:[1,128],139:$VB,140:$VC},{12:130,13:131,27:62,28:$V1,29:49,30:$V2,31:72,32:$V3,33:$V4,35:51,36:$V5,37:$V6,39
defaultActions: {60:[2,54],61:[2,55],96:[2,113],203:[2,93]},
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
parseError: function parseError(str, hash) {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
if (hash.recoverable) {
this.trace(str);
} else {
throw new Error(str);
}
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
},
parse: function parse(input) {
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
var self = this, stack = [0], tstack = [], vstack = [null], lstack = [], table = this.table, yytext = '', yylineno = 0, yyleng = 0, recovering = 0, TERROR = 2, EOF = 1;
'->*' and '=>*' now produce generators
2013-12-20 02:08:25 +00:00
var args = lstack.slice.call(arguments, 1);
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
var lexer = Object.create(this.lexer);
var sharedState = { yy: {} };
for (var k in this.yy) {
if (Object.prototype.hasOwnProperty.call(this.yy, k)) {
sharedState.yy[k] = this.yy[k];
}
}
lexer.setInput(input, sharedState.yy);
sharedState.yy.lexer = lexer;
sharedState.yy.parser = this;
if (typeof lexer.yylloc == 'undefined') {
lexer.yylloc = {};
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
}
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
var yyloc = lexer.yylloc;
revised patch for #1234; consolidated Value#push and Value#concat into Value#add; removed unnecessary INDEX_PROTO
2011-08-12 17:38:34 +00:00
lstack.push(yyloc);
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
var ranges = lexer.options && lexer.options.ranges;
if (typeof sharedState.yy.parseError === 'function') {
this.parseError = sharedState.yy.parseError;
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
} else {
this.parseError = Object.getPrototypeOf(this).parseError;
}
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
function popStack(n) {
stack.length = stack.length - 2 * n;
new version of Jison vendored ... rebuild the grammar, tests pass.
2010-04-22 02:52:20 +00:00
vstack.length = vstack.length - n;
revised patch for #1234; consolidated Value#push and Value#concat into Value#add; removed unnecessary INDEX_PROTO
2011-08-12 17:38:34 +00:00
lstack.length = lstack.length - n;
new version of Jison vendored ... rebuild the grammar, tests pass.
2010-04-22 02:52:20 +00:00
}
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
_token_stack:
function lex() {
var token;
token = lexer.lex() || EOF;
if (typeof token !== 'number') {
token = self.symbols_[token] || token;
}
return token;
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
}
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
var symbol, preErrorSymbol, state, action, a, r, yyval = {}, p, len, newState, expected;
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
while (true) {
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
state = stack[stack.length - 1];
ahh, finally. switched up our Jison configuration to provide better syntax errors. Now you get the unexpected token, instead of the expected one.
2010-06-02 00:21:12 +00:00
if (this.defaultActions[state]) {
action = this.defaultActions[state];
} else {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
if (symbol === null || typeof symbol == 'undefined') {
ahh, finally. switched up our Jison configuration to provide better syntax errors. Now you get the unexpected token, instead of the expected one.
2010-06-02 00:21:12 +00:00
symbol = lex();
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
}
ahh, finally. switched up our Jison configuration to provide better syntax errors. Now you get the unexpected token, instead of the expected one.
2010-06-02 00:21:12 +00:00
action = table[state] && table[state][symbol];
}
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
if (typeof action === 'undefined' || !action.length || !action[0]) {
var errStr = '';
new version of Jison vendored ... rebuild the grammar, tests pass.
2010-04-22 02:52:20 +00:00
expected = [];
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
for (p in table[state]) {
if (this.terminals_[p] && p > TERROR) {
expected.push('\'' + this.terminals_[p] + '\'');
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
}
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
}
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
if (lexer.showPosition) {
errStr = 'Parse error on line ' + (yylineno + 1) + ':\n' + lexer.showPosition() + '\nExpecting ' + expected.join(', ') + ', got \'' + (this.terminals_[symbol] || symbol) + '\'';
Removing the last Jison hack. (Jison 0.1.25)
2010-10-28 05:39:35 +00:00
} else {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
errStr = 'Parse error on line ' + (yylineno + 1) + ': Unexpected ' + (symbol == EOF ? 'end of input' : '\'' + (this.terminals_[symbol] || symbol) + '\'');
new version of Jison vendored ... rebuild the grammar, tests pass.
2010-04-22 02:52:20 +00:00
}
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
this.parseError(errStr, {
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
text: lexer.match,
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
token: this.terminals_[symbol] || symbol,
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
line: lexer.yylineno,
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
loc: yyloc,
expected: expected
});
new version of Jison vendored ... rebuild the grammar, tests pass.
2010-04-22 02:52:20 +00:00
}
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
if (action[0] instanceof Array && action.length > 1) {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
throw new Error('Parse Error: multiple actions possible at state: ' + state + ', token: ' + symbol);
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
}
switch (action[0]) {
case 1:
stack.push(symbol);
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
vstack.push(lexer.yytext);
lstack.push(lexer.yylloc);
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
stack.push(action[1]);
symbol = null;
if (!preErrorSymbol) {
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
yyleng = lexer.yyleng;
yytext = lexer.yytext;
yylineno = lexer.yylineno;
yyloc = lexer.yylloc;
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
if (recovering > 0) {
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
recovering--;
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
}
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
} else {
symbol = preErrorSymbol;
preErrorSymbol = null;
updating Jison
2010-02-13 23:19:59 +00:00
}
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
break;
case 2:
len = this.productions_[action[1]][1];
yyval.$ = vstack[vstack.length - len];
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
yyval._$ = {
first_line: lstack[lstack.length - (len || 1)].first_line,
last_line: lstack[lstack.length - 1].last_line,
first_column: lstack[lstack.length - (len || 1)].first_column,
last_column: lstack[lstack.length - 1].last_column
};
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
if (ranges) {
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
yyval._$.range = [
lstack[lstack.length - (len || 1)].range[0],
lstack[lstack.length - 1].range[1]
];
Allowing both end-points of slices to be implicit.
2011-12-21 00:21:26 +00:00
}
'->*' and '=>*' now produce generators
2013-12-20 02:08:25 +00:00
r = this.performAction.apply(yyval, [
yytext,
yyleng,
yylineno,
Make CoffeeScript work with jison 0.4.14+ Since zaach/jison commit 3548861b, `parser.lexer` is never modified anymore (a copy of it is made, and that copy is modified instead). CoffeeScript itself modifies `parser.lexer` and then accesses those modifications in the custom `parser.yy.parseError` function, but that of course does not work anymore. This commit puts the data that `parser.yy.parseError` needs directly on the `parser` so that it is not lost. Supersedes #3603. Fixes #3608 and zaach/jison#243.
2015-01-15 16:47:07 +00:00
sharedState.yy,
'->*' and '=>*' now produce generators
2013-12-20 02:08:25 +00:00
action[1],
vstack,
lstack
].concat(args));
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
if (typeof r !== 'undefined') {
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
return r;
}
if (len) {
stack = stack.slice(0, -1 * len * 2);
vstack = vstack.slice(0, -1 * len);
lstack = lstack.slice(0, -1 * len);
}
stack.push(this.productions_[action[1]][0]);
vstack.push(yyval.$);
lstack.push(yyval._$);
newState = table[stack[stack.length - 2]][stack[stack.length - 1]];
stack.push(newState);
break;
case 3:
return true;
Fixes #2274 -- allow @variables as loop variables
2012-04-24 16:21:47 +00:00
}
the parser seems too big to compile
2010-01-31 04:17:36 +00:00
}
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
return true;
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
}};
'->*' and '=>*' now produce generators
2013-12-20 02:08:25 +00:00
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
function Parser () {
this.yy = {};
}
Parser.prototype = parser;parser.Parser = Parser;
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
return new Parser;
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
})();
Better handling of initial indent at file start. * Detect initial indentation before the first token and enforce it. * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).
2013-06-13 22:21:47 +00:00
revised patch for #1234; consolidated Value#push and Value#concat into Value#add; removed unnecessary INDEX_PROTO
2011-08-12 17:38:34 +00:00
if (typeof require !== 'undefined' && typeof exports !== 'undefined') {
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
exports.parser = parser;
Parse compound assignment followed by a terminator. Closes #2532.
2012-11-28 01:11:01 +00:00
exports.Parser = parser.Parser;
Revert #2599
2013-02-28 13:37:30 +00:00
exports.parse = function () { return parser.parse.apply(parser, arguments); };
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
exports.main = function commonjsMain(args) {
Revert #2599
2013-02-28 13:37:30 +00:00
if (!args[1]) {
console.log('Usage: '+args[0]+' FILE');
process.exit(1);
removing our vendor'd copy of Jison ... you should install it from NPM now.
2010-06-28 04:26:45 +00:00
}
Revert #2599
2013-02-28 13:37:30 +00:00
var source = require('fs').readFileSync(require('path').normalize(args[1]), "utf8");
removing our vendor'd copy of Jison ... you should install it from NPM now.
2010-06-28 04:26:45 +00:00
return exports.parser.parse(source);
Revert #2599
2013-02-28 13:37:30 +00:00
};
nagated relational operators are now grouped into NOT_RELATED, fixing #720
2010-10-05 15:43:44 +00:00
if (typeof module !== 'undefined' && require.main === module) {
Revert #2599
2013-02-28 13:37:30 +00:00
exports.main(process.argv.slice(1));
It's beginning to come alive.
2010-02-11 04:24:05 +00:00
}
Fixes #2359 -- tweak grammar to use new name
2013-02-14 03:34:32 +00:00
}