Binding a C function wit FILE* object

Binding a C function wit FILE* object

[Victor Porton]

I am writing thick bindings for Raptor C library.

What should I do regarding the following function?

int raptor_uri_print (const raptor_uri *uri, FILE *stream);

The trouble is that Ada probably has no interface with FILE* objects.

The simplest thing is just to omit binding this particular function 
altogether. Are there other variants?

-- 
Victor Porton - http://portonvictor.org

Re: Binding a C function wit FILE* object

[Dan'l Miller]

On Sunday, July 27, 2014 10:45:20 AM UTC-5, Victor Porton wrote:
> I am writing thick bindings for Raptor C library.

No, as multiple people keep implying or keep telling you overtly:  you are writing a thin binding.  If you are asking how to represent a pointer to FILE almost directly in Ada, then clearly you are writing a thin binding.  Perhaps a thin binding is best for what you envision, but be clear in your thinking what you are and what you are not doing.

> What should I do regarding the following function?
> int raptor_uri_print (const raptor_uri *uri, FILE *stream);
> The trouble is that Ada probably has no interface with FILE* objects.

In a thick binding, Ada would have its own first-class-citizen representation roughly analogous to FILE (not pointer to FILE), such as a tagged record for byte-streams in general from which each format of file is derived into subclasses.

Re: Binding a C function wit FILE* object

[Victor Porton]

Dan'l Miller wrote:

> On Sunday, July 27, 2014 10:45:20 AM UTC-5, Victor Porton wrote:
>> I am writing thick bindings for Raptor C library.
> 
> No, as multiple people keep implying or keep telling you overtly:  you are
> writing a thin binding.  If you are asking how to represent a pointer to
> FILE almost directly in Ada, then clearly you are writing a thin binding. 
> Perhaps a thin binding is best for what you envision, but be clear in your
> thinking what you are and what you are not doing.
> 
>> What should I do regarding the following function?
>> int raptor_uri_print (const raptor_uri *uri, FILE *stream);
>> The trouble is that Ada probably has no interface with FILE* objects.
> 
> In a thick binding, Ada would have its own first-class-citizen
> representation roughly analogous to FILE (not pointer to FILE), such as a
> tagged record for byte-streams in general from which each format of file
> is derived into subclasses.

Most of my bindings are thick enough, but for this particular function I've 
made a thin binding (however it throws an exception instead of returning 
error value).

-- 
Victor Porton - http://portonvictor.org