On 2/20/2012 3:36 PM, Paul H. Hargrove wrote:
NOTE: I've not yet actually tested the resulting show_help utility
[but soon].
An "instrumented" version of test/opal_sos.c is getting the same string
back from opal_show_help_string() both with and without my patch. So, I
believe it to be cor
Thanks! I'll have to move to another machine to test, though - my Mac Lion is
running flex 2.5.35, and I no longer see those warnings. Interesting as I was
under the impression that flex is no longer supported….
On Feb 20, 2012, at 4:36 PM, Paul H. Hargrove wrote:
> Ralph,
>
> The change belo
Ralph,
The change below removes the warning, but very slightly changes the
syntax that is parsed.
In the original, anything following the "[tag]" was considered trailing
context.
However that made inputs like "[tag]foo]" ambiguous to the parser (hence
the warning).
With the change below, both
My bad - didn't look closely enough. I'll take a look at it and see if there is
anything we can do.
On Feb 20, 2012, at 4:12 PM, Paul H. Hargrove wrote:
> Ralph,
>
> Are you sure this is a flex-generated file?
> I am looking at opal/util/show_help_lex.l in the svn trunk and it certainly
> look
Ralph,
Are you sure this is a flex-generated file?
I am looking at opal/util/show_help_lex.l in the svn trunk and it
certainly looks human-generated to me.
Please clue me in if I am missing something.
The warning is from flex when processing the .l file, NOT from the
compilation of the flex-g
We get that everywhere, unfortunately - it comes from flex and is outside our
control as the file it complains about is actually generated by flex itself.
Unfortunately, flex is no longer maintained, and so nothing has been done to
correct it.
On Feb 19, 2012, at 8:47 PM, Paul H. Hargrove wrot
