[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pdf-devel] Hash module API
From: |
gerel |
Subject: |
Re: [pdf-devel] Hash module API |
Date: |
Sun, 06 Apr 2008 15:37:58 -0300 |
> Date: Sun, 06 Apr 2008 18:45:25 +0200
> From: address@hidden
>
> `pdf_status_t pdf_hash_mapkeys (hash_table,
> pdf_hash_mapkeys_fn_t func,
> void *client_data)'
>
> Apply FUNC to each element contained in HASH_TABLE. The prototype
> of FUNC should be:
>
> pdf_status_t func (pdf_hash_t hash_table, char *key, void
> *client_data)
>
> FIXME: Should we define an order???
If there exists a situation in wich order is relevant then we can define an
iterator type over the keys or elements instead of the "pdf_hash_mapkeys()"
function.
Something like:
'pdf_status_t pdf_hash_iterator (hash_table, order_type, itr_pointer)'
and
'pdf_status_t pdf_hash_iterator_next (itr_pointer, next_key / next_element)'
>
>
> I don't know how the enum "pdf_hash_value_type_e" is going to be
> used yet.
>
> We are not going to use that type, since we are working with generic
> pointers to store data into the hash table. The definition of
> `pdf_hash_value_type_e' in gnupdf.texi should be deleted.
>
I agree.
I'll add the rest of the functions you suggested.
cheers
-gerel
- [pdf-devel] Hash module API, gerel, 2008/04/05
- Re: [pdf-devel] Hash module API, gerel, 2008/04/05
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/06
- Re: [pdf-devel] Hash module API,
gerel <=
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/06
- Re: [pdf-devel] Hash module API, gerel, 2008/04/06
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/07
- Re: [pdf-devel] Hash module API, gerel, 2008/04/07
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/08
- Re: [pdf-devel] Hash module API, gerel, 2008/04/09
- Re: [pdf-devel] Hash module API, gerel, 2008/04/09
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/10
- Re: [pdf-devel] Hash module API, jemarch, 2008/04/10
- Re: [pdf-devel] Hash module API, gerel, 2008/04/10