poke-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Roadmap for 1.4 and 2.0


From: Jose E. Marchesi
Subject: Roadmap for 1.4 and 2.0
Date: Thu, 02 Dec 2021 00:26:31 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Hi people!

We have done some triage of issues in poke.rec and other stuff we had in
private todo lists.

Find the result below (see details of each item in etc/poke.rec).

1.4 is scheduled for ASAP.
2.0 is scheduled for February 2022.

1.4

Summary: Support %% in printf string literals
Summary: Fix %destructors in parser
Summary: Do not leak decl AST nodes in parser
Summary: Remove call to `abort' in pkl-lex.l
Summary: Complete C and Poke printers for function types
Summary: Function types are generated with its arguments reversed
Summary: Pass the declaration's pk_value in callback pk_map_decl_fn
Summary: .set with no arguments should give a summary of all options

2.0

Summary: Alignment attribute in struct types
Summary: Operator to upunit an offset
Summary: casts from integral to array and from array to integral
Summary: Support a pipe IOS
Summary: Support nested integral structs
Summary: Support for struct deintegrators
Summary: Alien tokens for IO space names: $<path/to/file>
Summary: Add error recovery support to the compiler
Summary: unify `break' and `continue' in the same AST node
Summary: Consider struct types as complete if all labels are literal
Summary: Unions can be completed
Summary: Union fields should not refer to other fields
Summary: `load' doesn't load after an error
Summary: Support for string properties
Summary: Make the PVM aware of units
Summary: Add `strtok' to the standard library
Summary: Auto-complete value attributes
Summary: Auto-complete yes|no in commands
Summary: .info type TYPENAME
Summary: .vm time
Summary: parallelize the dg testsuite
Summary: add mutex to avoid concurrency crash with hyperlinks
Summary: support casts from `any' to function types
Summary: support references to values in the MI protocol



reply via email to

[Prev in Thread] Current Thread [Next in Thread]