Re: Interfacing to void *

[Keith Thompson <kst@cts.com>]

William Starner <billeug@worldnet.att.net> writes:
> If I'm trying to interface to a C library that uses this struct
> 
> struct BigNum {
> 	void *ptr;
> 	unsigned int size;
> 	unsigned int allocated;
> };
> 
> how should I interface to void*?
> 
> I have
> private
> 	type voidpointer is access character;
> 	type BigNum is record 
> 		ptr: voidpointer;
> 		size: Interfaces.C.unsigned;
> 		allocated: Interfaces.C.unsigned;
> 	end record;
> 	type RealBigNum is access BigNum;
> 	type UnboundedInt is new Linear with record
> 		Value: RealBigNum;
> 	end record;
> end nla23.linear.bnlib;
> but char* = void* is a C rule, not an Ada rule. It probably works,
> but it's not right. (I don't need to access anything through that
> pointer.)

You're not 100% guaranteed that an Ada type declared as "access
Character" is compatible with a C "char*", or even that Ada's type
Character is the same as C's char.

My suggestion:

    type Void_Pointer is private;
    Null_Void_Pointer : constant Void_Pointer;
    ...
    type Void_Pointer is new Interfaces.C.Strings.chars_ptr;
    Null_Void_Pointer : constant Void_Pointer
        := Interfaces.C.Strings.Null_Ptr;

By making it a private type, you avoid making the operations in
Interfaces.C.Strings visible to clients.

The closest semantic equivalent to C's void* is Ada's System.Address.
This is *almost* certain to be compatible (I doubt that there's an
existing system on which they're different), but the language doesn't
guarantee it.

-- 
Keith Thompson (The_Other_Keith) kst@cts.com  <http://www.ghoti.net/~kst>
San Diego Supercomputer Center           <*>  <http://www.sdsc.edu/~kst>
One of the great tragedies of ancient history is that Helen of Troy
lived before the invention of the champagne bottle.