Re: Interfaces.C + generics: stack overflow

["Randy Brukardt" <randy@rrsoftware.com>]

"hreba" <f_hreba@yahoo.com.br> wrote in message 
news:ejhckeF1tg7U1@mid.individual.net...
> My last posting was buried deep inside the thread and somewhat lengthy, so 
> here in a compact form. What works is (everything compiles and test 
> application executes):

I agree with Jeff, there's not enough detail here to even see if there is a 
bug or your mistake. We need to know how/where the generic is instantiated, 
where/how the access-to-function value is created, and probably more.

But let me say that the rules for access-to-subprogram types are different 
inside of generics than they are in normal packages, in order to allow for 
the possibility of generic sharing. That ought to manifest as compile-time 
errors and/or the raising of Program_Error, so it seems that there might be 
a compiler bug in your code. But to find that, one needs to see the whole 
thing, not just a little corner.

If you really want to write portable interfacing code, you would not use any 
generics in the raw interface. (Have the generics call non-generic interface 
code with appropriate type conversions.) Janus/Ada doesn't allow any 
convention C stuff in generic units, because it is incompatible with the 
extra dope needed to implemented universal generic sharing. I'd expect 
something similar to happen for any implementation that supports almost any 
form of generic sharing. (If you only care about GNAT, do what ever you 
want.)

                              Randy.