According to Geoff Hutchison:
> OK, at this point, I *think* I have everything pretty much set for
> 3.2.0b2. I'll be cleaning up the docs a bit, but I don't know of any code
> changes that need to be made. (It turned out the problem with
> build_select_lists is that the parser didn't like lists of numbers...)
>
> I'm about to roll a pre-release. If I don't hear complaints, I'll roll the
> release on Monday night my time, about 30 hrs from now, give-or-take. The
> pre-release will be available in
> <http://www.htdig.org/files/snapshots/htdig-3.2.0b2pre.tar.gz>
>
> So I'll say it clearly--if there's something missing or still broken,
> speak up ASAP!
I'm still not satisfied with the config parser. Unless I'm misreading
the grammar, it looks like there are a lot of potential problems lurking
in it. It seems that for the value of any parameter, it will only allow
a string, a number or a list, where a list is defined as:
list: T_STRING T_STRING
| list T_STRING
| list T_NUMBER
But in reality, it should be possible to set an attribute's value to
just about anything. The grammar defines these as valid tokens:
%token NUM T_DELIMITER T_NEWLINE T_RIGHT_BR T_LEFT_BR T_SLASH
%token <str> T_STRING T_KEYWORD T_NUMBER
so that leaves a lot of tokens that it will not allow within
a list. Aren't keywords allowed as attribute values? After all,
build_select_lists allows (even requires) that some of the list items
be attribute names, which the grammar seems to treat as T_KEYWORD.
What about a list that begins with a number? The list syntax seems to
require lists to begin with at least two strings.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
