#1401 closed bug (fixed (in master))
parser_parse() fails to parse "char str" specifications properly.
| Reported by: | myshkin | Owned by: | myshkin |
|---|---|---|---|
| Milestone: | 3.3.0 | Keywords: | cleanup utils |
| Cc: |
Description
The test parse/parser/char1 currently fails. Its specification is "test-char1 char c0 int i0 char c1 str s", but with input "test-char1:::34:::lala", it assigns ":lala" to the string s. There is an unusual interaction between the strtok() call for char handling and a subsequent call to strtok() for string handling. This does not appear to happen for other types that precede strings.
Change History (3)
comment:1 Changed 10 years ago by myshkin
- Owner set to myshkin
- Status changed from new to assigned
comment:2 Changed 10 years ago by myshkin
- Status changed from assigned to pending
comment:3 Changed 10 years ago by magnate
- Resolution set to fixed
- Status changed from pending to closed
In nightlies as of 17th April [r2d17857]
Note: See
TracTickets for help on using
tickets.
Now fixed in myshkin/staging. parser_parse() now skips ahead one more character when parsing character tokens.