Tue, 16 Jun 2015 06:45:26 +0100 Fix in codegen for inlined sequence nodes.
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 16 Jun 2015 06:45:26 +0100] rev 489
Fix in codegen for inlined sequence nodes. For inlined sequence nodes, generate nested ifs rather than sequential code which does not work when inlined. The reason is that #codeReturn: in inline generates instvar assignment, not method return, so in sequential code the next child of a sequence will be probed even if previous failed. If that happends, the whole sequence fail and therefore we must generate nested ifs to correctly handle this w.r.t. inlining.
Mon, 15 Jun 2015 19:13:49 +0100 Avoid creation of intermediate collection for mapped action nodes.
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 15 Jun 2015 19:13:49 +0100] rev 488
Avoid creation of intermediate collection for mapped action nodes.
Mon, 15 Jun 2015 18:00:44 +0100 Fix in codegen: fixed compilation of unknown node: do not hardcode return variable name
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 15 Jun 2015 18:00:44 +0100] rev 487
Fix in codegen: fixed compilation of unknown node: do not hardcode return variable name ...use `self retvalVar` instead
Mon, 15 Jun 2015 17:47:38 +0100 Renamed #codeStoreValueOf:intoVariable: to #codeAssignParsedValueOf:to:
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 15 Jun 2015 17:47:38 +0100] rev 486
Renamed #codeStoreValueOf:intoVariable: to #codeAssignParsedValueOf:to: to use same naming as #codeAssign:to:
Mon, 15 Jun 2015 17:12:54 +0100 Fixed codegen for empty (mapped) action block.
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 15 Jun 2015 17:12:54 +0100] rev 485
Fixed codegen for empty (mapped) action block. Although empty blocks are useless in practice, they may occur (and do occur in tests)
Fri, 05 Jun 2015 00:05:08 +0100 Do not create intermediate collection when parsing sequence if not necesary.
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 05 Jun 2015 00:05:08 +0100] rev 484
Do not create intermediate collection when parsing sequence if not necesary. The collection is not needed when the result of a choice is being used in mapped parser. In that case, store parsed objects in variables and inline action code to use these variables to access parsed objects.
Wed, 03 Jun 2015 09:06:49 +0100 Oops, fixed subproject definition (wrong package names)
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 03 Jun 2015 09:06:49 +0100] rev 483
Oops, fixed subproject definition (wrong package names)
Wed, 03 Jun 2015 08:48:59 +0100 Updated .mcz exporting code to include a commit message digest
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 03 Jun 2015 08:48:59 +0100] rev 482
Updated .mcz exporting code to include a commit message digest ...instead of just exported revision commit message.
Wed, 03 Jun 2015 06:23:49 +0100 Introduced PPCMappedActionNode for PPMappedActionParser.
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 03 Jun 2015 06:23:49 +0100] rev 481
Introduced PPCMappedActionNode for PPMappedActionParser. It's compilation is not yet ideal, bot works for now.
Tue, 02 Jun 2015 17:25:57 +0100 Introduced PPMappedActionParser, a specialized parser for map:ped actions.
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 02 Jun 2015 17:25:57 +0100] rev 480
Introduced PPMappedActionParser, a specialized parser for map:ped actions. In order to compile nicer code, compiler has to be able to tell between simple (==>) action parser and mapped (map:) action parser.
(0) -300 -100 -10 +10 +100 tip