Sorry about posting to htdig-general before. I meant to specify
htdig-dev, really. I've moved it back now.
According to J. op den Brouw:
> On Tue, 13 Mar 2001, Gilles Detillieux wrote:
> > 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.
>
> Hmm, sorry for this, but I *love* good software that's free and do *not*
> love software that's buggy and cost a forture.....
I agree with you totally. That's why we're using Linux and GNU tools more
and more here. However, it can be a bit of a pain when you're trying to
get one package going, and you end up having to install one or several
more other packages just to get this one thing working. It's even worse
when you feel you already have the right package installed, but you need
to install another one like it, not because of a bug in the existing code,
but because of a needless version-specific quirk in the package you're
trying to install. All I'm saying is we should try to avoid these quirks
wherever possible, and allow our users to choose the tools they prefer
if at all possible, rather than making the decision for them.
> > 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.
>
> Of course I will try, but I forgot to save your changes. Can you send me again?
Well, it was quoted in my last message to you, but in case you've already
deleted that too, here it is again...
> > > "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.
To summarise, use octal constants in the character class on line 46,
and add a newline on line 110, right between the "{" and the comment.
Thanks.
--
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-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
