On Mon, Aug 25, 2014 at 08:04:16PM +0100, Dominik Vogt wrote:
> On Mon, Aug 25, 2014 at 07:48:53PM +0100, Thomas Adam wrote:
> > On Sun, Aug 24, 2014 at 02:08:25AM +0100, Dominik Vogt wrote:
> > > Maybe you can keep an eye out for rules common to multiple
> > > commands. Possible things that come to my mind:
> > >
> > > * Coordinate prefixes and suffixed from move-type commands.
> > > * Width and height prefixes and suffixes from resize type
> > > commands.
> > > * Many commands accept either BOOL arguments of BOOL_OR_TOGGLE.
> >
> > This works is on-going here (origin/ta/parser-common-types):
> >
> > https://github.com/ThomasAdam/mvwm/tree/ta/parser-common-types
> >
> > Apologies for it being so slow, this weekend turned out to be busier
> > than I'd hoped.
>
> No need to apologise for anything. Maybe, if we could agree that
> you work through the command list from the beginning, I could do
> some work at the end when there's time.
And eventually meet in the middle? :) OK, I can do that. I fear
though that working from the end you're going to encounter a slightly
harder time in terms of definition.
Note that we're accumulating a number of outstanding definition, notably
these:
TOKEN
STRING
RESTOFLINE
RESTOFLINE_COMMAND
In my mind, all of these boil down to either an option, or a
command---certainly in the case of TOKEN/STRING; there's very little
semantic difference between the two.
With respect to RESTOFLINE/RESTOFLINE_COMMAND, are these syntatic
placeholders for specific things, or can these be generalised to either
OPTION and COMMAND, respectively?
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
