[Top][All Lists]

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

Re: why does "integer" in q2c now parse a list?

From: John Darrington
Subject: Re: why does "integer" in q2c now parse a list?
Date: Thu, 11 Nov 2004 12:05:41 +0800
User-agent: Mutt/1.3.28i

On Wed, Nov 10, 2004 at 07:43:17PM -0800, Ben Pfaff wrote:
     The q2c input format allows "integer" and "integer list" as value
     types.  The former is supposed to parse a single integer, the
     latter an arbitrary number of integers.  But it looks like you
     changed it so that "integer" also parses a list of integers.  I
     don't understand; why?

I extended the semantics slightly.

"integer" and "double" still parse a single value, and 
"{integer,double} list" still parse arbitrary # of values.

The difference is, that previously, "integer" did not allow a value to
be given multiple times. (Actually IIRC, the parser allowed it, but
the value overwrote any previous ones).

Some commands have {integer,double} subcommands for which it is
meaningful to say:

COMMAND /var = x, y
        /SUBCMD 3
        /SUBCMD 99
        /SUBCMD 42

and for this to have different semantics to: 

COMMAND /var = x, y
        /SUBCMD 3, 99, 42


PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See or any PGP keyserver for public key.

Attachment: pgpD3GQtrPMh1.pgp
Description: PGP signature

reply via email to

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