[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bison-20001221

From: Hans Aberg
Subject: Re: bison-20001221
Date: Sat, 13 Jan 2001 16:57:18 +0100

At 09:11 -0500 1-01-13, Jesse Thilo wrote:
>> Actually, it is a pretty normal thing to modify library files: Just make a
>> local copy of the sources, and if the includes are "..." it will be read
>> before any library file. At least my linker overrides a library duplicate
>> names.
>You are missing the point somewhat.  We're not talking about
>overriding standard C library functions.  We're talking about support
>files written *for GNU software* and used by several GNU programs.  If
>such a file needs fixing, it needs fixing everywhere.

Not necessarily. If the library function does not work as is with your
particular program, one can modify it. Very convenient.

>  There is little
>to be gained in keeping forked versions in Bison (or any other GNU
>program): it adds to the maintenance effort, it detracts development
>from where it should be, and it denies the benefit of any fixes to
>other program maintainers.

Well, it is obvious that if one modifies a library file, one has to keep
track of updates of it too, as well. That is, if it is needed: After all,
you included a modified version of it that seems to work better with your
program, so updates are probably not so needed then. :-)

>You can argue with us all you want, but we're not going to maintain
>our own versions of those files.

Well, you are free to do whatever you want. -- I just point out some rather
standard development possibilities to you. :-)

>  If you think they need fixing,
>bug-bison is not the place to report the problems.  After all, if you
>have to change those files to port Bison, you'll need to make the same
>exact changes to any other GNU program that uses those files.

Well, I figure you are free to decide what ought to be reported on this list.

However, there are many strategies coping with a problem in a library file,
one is to make a modified copy of the library file itself (as described
above), another is perhaps writing separate source code, and yet another is
to make use of another library.

None of these approaches seems to have anything with the developers of the
original library to do. :-)

In addition, I do not know if you ever have reported a library problem to
the maintainers of that library and hoping for a fix. :-) If the fix at all
will occur, it usually takes a considerable time for it too happen.

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]