Re: Passing a String to a C/C++ Subprogram (Special Case)

[Eryndlia Mavourneen <eryndlia@gmail.com>]

On Thursday, October 17, 2013 8:58:51 AM UTC-5, sbelm...@gmail.com wrote:
> If the client might not be in C anyway, I would put the onus on other units to sort it all out.  Even if a non-C client can be written to figure out a C string, who says the client language can be exported as C convention?  Better to isolate it entirely for when they inevitably change their minds.
> 
> generic
>    type Client_String_Type is private;
>    with function Convert_To_Client(x : String) return Client_String_Type;
>    with procedure External_Prog (y : in Client_String_Type);
> ...
> begin 
>    ...
>    External_Prog (Convert_To_Client("Hello World!"));
>    ...
> 
> -sb

Interesting approach.

I am assuming that the pragmas Convention and Import will do their jobs properly, and anyway, forcing a generic on the clients is almost certain to be rejected.

-- Eryndlia Mavourneen (KK1T)