[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdf-devel] Public API and gl_list
From: |
jemarch |
Subject: |
Re: [pdf-devel] Public API and gl_list |
Date: |
Sun, 09 Mar 2008 09:36:12 +0100 |
User-agent: |
Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
> As we already discussed, Gnulib headers should not be modified in your
> source tree (then you can't update them), or installed by make install
> (then there are collisions).
>
> If you want to use them in the PDF public headers, then physically
> insert them into your headers so there is no file named "gl_list.h" that
> gets installed (or modified). Otherwise, just don't use them.
Ok, I'm going to do that. My point was that extra work will be needed anyway.
An alternative would be to define pdf_list_t, pdf_list_iterator_t, etc
much like the following:
struct pdf_list_s
{
void *gl_list;
/* Maybe more information... extensions, etc */
};
typedef pdf_list_s *pdf_list_t;
Then we can include gl_array_list.h in pdf-list.c and really use the
gnulib module in an internal way. For example:
#include <gl_array_list.h>
[...]
inline pdf_status_t
pdf_list_destroy (pdf_list_t list)
{
gl_list_free ((gl_list_t) list->gl_list);
return PDF_OK;
}
- [pdf-devel] Public API and gl_list, gerel, 2008/03/08
- Re: [pdf-devel] Public API and gl_list, Karl Berry, 2008/03/08
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/08
- Re: [pdf-devel] Public API and gl_list, Aleksander Morgado, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, jemarch, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, jemarch, 2008/03/10
- Re: [pdf-devel] Public API and gl_list, gerel, 2008/03/10