Prexonite 1.2.2 Beta

Theme "Generalization of Macros"

Closed:

15 | Active:

0 (0 in Test) |

Invested hours: 53.7

Burndown

Export: CSV | XML | RSS Feed | Print

#	Summary	Status
34	Macro commands	Fixed
37	Make partially applicable macros possible	Fixed
39	Rewrite macro-system to use only 1 shared variable	Fixed
61	Prx: Display warning and info messages	Fixed
62	Prx: Improve error message for missing entry function	Fixed
63	Bugs/Refactoring Milestone 1.2.2	Fixed
64	Bug in Code Generation of BlockExpression	Fixed
65	Bug in code generation of ObjectCreation	Fixed
67	Rewrite call\macro as macro command	Fixed
69	Make call\macro partially applicable	Fixed
71	psr/console.pxs: Fields with unspecified length cannot be cleared	Fixed
75	Make call partially applicable (with call\* support)	Fixed
76	Make call\member partially applicable (with call\*)	Fixed
77	Make call\async partially applicable (with call\*)	Fixed
78	Make call\tail partially applicable (with call\*)	Fixed

Release Level: Beta

Prexonite v1.2.2

New: Macro commands (= macros implemented in managed code)
New: Macros can now handle partial application (must happen explicitly)
New: Prx.exe now displays warnings and info messages. Warnings are on by default, info messages are off by default.
New: New calling convention: call\star, allows for more flexible partial application of call/*-type functions/commands/macros.
Fixed: code generation of block expression
Fixed: optimization of object creation could re-order arguments
Fixed: psr\console.pxs - Fields with an unspecified length work again
Change: call\macro is not implemented as a macro command
Change: Macro system now uses only 1 shared variable: context. Some of the old macro variables no longer work. You'll get nice compiler errors/warnings.
Change: Missing entry function no longer displays a stack trace.
Change: call, call\member, call\tail, call\async and call\macro are now implemented as macros to take advantage of call\star

Incorrect uses of ToUpper/ToLower/ToDouble/etc. (using default culture)
Creating a BlockExpression that contains jumps with targets outside that block can lead to invalid byte code being generated
Comments at the end of a script file can cause a compile error. Workaround: Add a new line that contains just `{}`.