Le 21/06/2013 15:03, Jeff Squyres (jsquyres) a écrit :
Can you submit a combined patch when ready?
Ok, i'll make a combined lex patch.
On Jun 21, 2013, at 7:40 AM, Piotr Lesnicki wrote:
> 1) you are right, an eof in the middle of a section must be
> handled explicitly, otherwise it ends by an unrelated error later,
> just as it currently does. By the way, here it ends with
> [no-options-error] which has no corresponding m
Hi,
1) you are right, an eof in the middle of a section must be
handled explicitly, otherwise it ends by an unrelated error later,
just as it currently does. By the way, here it ends with
[no-options-error] which has no corresponding message in
'help-opal-wrapper.txt'.
I joined t
Piotr --
Many thanks for the patch. Sorry, our lex is quite a bit rusty, and it took us
quite a while to look at this. :-\
I have a few questions:
1. What happens if the file ends while in ? E.g., if a the last line
of the file is "/* Hello".
2. Does this same kind of fixup need to be appl
Hi,
The parser of key/value configuration files (like
'openmpi-mca-params.conf') has some small bugs:
- a parsing error occurs when there is no new line at the end of the
file (and the error shows while reading the next conf file)
- error messages display wrong line numbers
- error messages sh
