According to J. op den Brouw:
> Installing flex cured the problem. Maybe we should insist
> on installing flex when builing htdig on a box.

Yuck!  I hate adding requirements like that on users.  It's bad enough
that we now require GNU make, and still have a lot of difficulty with
non-GNU compilers.  You shouldn't need to replace all your development
environment with GNU tools just to compile a program.  I'd rather insist
on at least attempting to write portable code before shifting the burden
on users like this.

Is there any way I can convince you to go back to lex and try the
two simple code changes I suggested?  I was really hoping to get some
portability feedback here.

> On Mon, 12 Mar 2001, Gilles Detillieux wrote:
> > According to J. op den Brouw:
> > > Sorry, but I'm absolutely not a lex & yacc user. And, strangely,
> > > I'm not able to get the version of this lex, but I think it's
> > > a crappy version of HP. I think I need to install flex...
> > > 
> > > Making all in htcommon
> > > make[1]: Entering directory
> > > `/pers/www/msql/Projects/Htdig/htdig-3.2.0b3-030401/htcommon'
> > > lex -L  conf_lexer.lxx && mv lex.yy.c conf_lexer.cxx
> > > "conf_lexer.lxx" line 85: warning 45: Non-portable Character Class
> > > "conf_lexer.lxx" line 100: warning 45: Non-portable Character Class
> > 
> > I think we probably should rewrite the STRING character class not to use
> > hex characters.  Just a hunch, but I think that's what it's complaining
> > about.  Try this on line 46, and see if it gets rid of those warnings:
> > 
> > STRING                      [\041-\377]+
> > 
> > > "conf_lexer.lxx" line 111: warning 22: Executable statements should occur right
> > > after %%
> > > "conf_lexer.lxx" line 117: warning 22: Executable statements should occur right
> > > after %%
> > > "conf_lexer.lxx" line 121: warning 22: Executable statements should occur right
> > > after %%
> > > "conf_lexer.lxx" line 123: error 81: syntax error
> > 
> > Now that's really odd, but I'd guess that lex got confused by the comment
> > right on the same line as the opening brace on line 110.  Try moving the
> > comment down a line, so that line 110 ends with the "{".
> > 
> > If these changes clear up these errors, we should commit them for the sake
> > of portability.

-- 
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

_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to