[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bison and i18n
From: |
Eli Zaretskii |
Subject: |
Re: bison and i18n |
Date: |
Fri, 03 Jun 2005 00:51:44 +0300 |
> Date: Thu, 2 Jun 2005 21:29:50 +0200
> From: Stepan Kasal <address@hidden>
>
> > fprintf(stderr, dgettext("bison-rt", "parse stack blown!\n"));
> >
> > Then all that's needed is some new autoconf/automake machinery to
> > include the .mo files from the bison used on the developer's machine
> > in the distribution, and then to install them if they're not there
> > on the installation machine (assuming that gettext is available).
>
> no, this is what would confuse the packaging mechanism of various
> distributions.
Please explain why this problem would happen. I don't think I
understand it.
> But there is another question:
> Yacc was invented before shared libraries were common, right?
> Shouldn't we stop and ask ourselves: isn't the yacc skeleton big enough,
> so that it would deserve to be moved to a separate library?
The answer to that questions is: NO, the Yacc skeleton isn't big
enough to be in a separate library. Even if you somehow solve the
problem pointed by Aharon with code fragments embedded in the parser.