* libihash/ihash.c: Cleanup #includes.
---
libihash/ihash.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/libihash/ihash.c b/libihash/ihash.c
index fe9eaed..e813f63 100644
--- a/libihash/ihash.c
+++ b/libihash/ihash.c
@@ -25,14 +25,12 @@
#include
#endif
> Well, you could store an ihash_t in the struct, which is a pointer.
> Why would you want to store the struct and use init/destroy? You need the
> address anyway when invocing the functions operating on it.
>
> Are you taking advantage of this in some code?
No, however, Thomas is. Take a look
On Sat, Mar 03, 2001 at 02:52:40PM +0100, Marcus Brinkmann wrote:
> On Tue, Feb 27, 2001 at 04:11:31PM +0100, Neal H Walfield wrote:
> > This patch allows users of the ihash library to include the ihash
> > structure directly in user structures, i.e.:
> >
> > struct foo
> > {
> > struct ihash;
On Tue, Feb 27, 2001 at 04:11:31PM +0100, Neal H Walfield wrote:
> This patch allows users of the ihash library to include the ihash
> structure directly in user structures, i.e.:
>
> struct foo
> {
> struct ihash;
> };
>
> Whereas before, this was not possible.
Well, you could store an ihash
This patch allows users of the ihash library to include the ihash
structure directly in user structures, i.e.:
struct foo
{
struct ihash;
};
Whereas before, this was not possible.
-Neal
Only in hurd-20010115/libihash: .primes.c.swp
diff -ur hurd-20010115-snapshot/libihash/ChangeLog hurd-200
