From: David Gibson <david@gibson.dropbear.id.au>
To: Kirill Smelkov <kirr@nexedi.com>
Cc: ccan@lists.ozlabs.org
Subject: Re: [PATCH] bitmap: Allow bitmap type to be forward declared
Date: Tue, 22 Oct 2019 16:25:20 +1100 [thread overview]
Message-ID: <20191022052520.GI6439@umbus.fritz.box> (raw)
In-Reply-To: <20191021150903.25159-1-kirr@nexedi.com>
[-- Attachment #1.1: Type: text/plain, Size: 2620 bytes --]
On Mon, Oct 21, 2019 at 03:09:20PM +0000, Kirill Smelkov wrote:
> Currently bitmap type is defined via untagged struct which makes it
> impossible to forward declare it. Forward-declaring is useful since all
> bitmap functions only use bitmap* and in public user-visible
> headers/datastructures it is enough to indicate that a data field with
> bitmap pointer is there, whereas bitmap.h can be included only in
> implementation.
>
> Beside that some headers are included by both C and C++ parts of a
> project, and when ccan/bitmap.h is processed by C++ compiler it gives:
>
> ./3rdparty/ccan/ccan/bitmap/bitmap.h: In function ‘bitmap* bitmap_alloc(long unsigned int)’:
> ./3rdparty/ccan/ccan/bitmap/bitmap.h:201:15: error: invalid conversion from ‘void*’ to ‘bitmap*’ [-fpermissive]
> return malloc(bitmap_sizeof(nbits));
> ~~~~~~^~~~~~~~~~~~~~~~~~~~~~
> ./3rdparty/ccan/ccan/bitmap/bitmap.h: In function ‘bitmap* bitmap_realloc0(bitmap*, long unsigned int, long unsigned int)’:
> ./3rdparty/ccan/ccan/bitmap/bitmap.h:227:18: error: invalid conversion from ‘void*’ to ‘bitmap*’ [-fpermissive]
> bitmap = realloc(bitmap, bitmap_sizeof(nbits));
> ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ./3rdparty/ccan/ccan/bitmap/bitmap.h: In function ‘bitmap* bitmap_realloc1(bitmap*, long unsigned int, long unsigned int)’:
> ./3rdparty/ccan/ccan/bitmap/bitmap.h:238:18: error: invalid conversion from ‘void*’ to ‘bitmap*’ [-fpermissive]
> bitmap = realloc(bitmap, bitmap_sizeof(nbits));
>
> -> Give to users ability not to force-include ccan/bitmap.h by
> forward-declaring bitmaps like this:
>
> typedef struct bitmap bitmap;
> ...
> struct MyStruct {
> bitmap *my_bitmap;
> };
>
> Cc: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Kirill Smelkov <kirr@nexedi.com>
Applied, thanks.
> ---
> ccan/bitmap/bitmap.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ccan/bitmap/bitmap.h b/ccan/bitmap/bitmap.h
> index beeb1e95..54382801 100644
> --- a/ccan/bitmap/bitmap.h
> +++ b/ccan/bitmap/bitmap.h
> @@ -21,7 +21,7 @@ typedef unsigned long bitmap_word;
> /*
> * We wrap each word in a structure for type checking.
> */
> -typedef struct {
> +typedef struct bitmap {
> bitmap_word w;
> } bitmap;
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
next prev parent reply other threads:[~2019-10-22 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 15:09 [PATCH] bitmap: Allow bitmap type to be forward declared Kirill Smelkov
2019-10-22 5:25 ` David Gibson [this message]
2019-10-22 7:53 ` Kirill Smelkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191022052520.GI6439@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=ccan@lists.ozlabs.org \
--cc=kirr@nexedi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).