On Tue, Aug 26, 2014 at 10:42:03PM +0100, Dominik Vogt wrote:
Pondering a new parser a bit, I think it would be good to split
the existing command implementations:
Hi,
To this end, I've created a new branch: 'new-parser' which will hold
this work. Thus far, I've renamed
On Tue, Aug 26, 2014 at 08:40:49PM -0400, Dan Espen wrote:
Thomas Adam tho...@fvwm.org writes:
* Tokenisation in the form key/value means that each command can lookup
the data in the same way. For instance:
if (has_token(level)) {
int l =
Pondering a new parser a bit, I think it would be good to split
the existing command implementations:
1. A user interface function that takes the F_CMD_ARGS argument
list as it does now. Its tasks are:
a) To prepare a structure that contains the syntax tables for
the command and any
On Tue, Aug 26, 2014 at 10:42:03PM +0100, Dominik Vogt wrote:
1. A user interface function that takes the F_CMD_ARGS argument
list as it does now. Its tasks are:
a) To prepare a structure that contains the syntax tables for
the command and any context information that is
Thomas Adam tho...@fvwm.org writes:
* Tokenisation in the form key/value means that each command can lookup
the data in the same way. For instance:
if (has_token(level)) {
int l = strtonum(get_token(level), 1, INT_MAX, NULL);
if (l 10)
