Ciao,
Il Gio, 28 Febbraio 2013 9:50 am, Torbjorn Granlund ha scritto:
> Richard Henderson <r...@twiddle.net> writes:
> We are at least aware of these things ("Calls and linkage"):
> https://gmplib.org/devel/GMPng.html
> But the first thing to do is to confirm exactly what API symbols
> should be exported. I'm going to begin with the assumption that if it
> isn't declared in gmp-h.in, then it's not public.
>
> We could start there, and wait for the screams. :-)
Our own test-suite will let the first scream out !-D
The first thing to do IMO is to define the levels of visibility we need:
we have documented functions, functions that are not documented but are
used by other programs (we should probably document many of those),
functions and tables that are used both internally and by the test-suite
(would be nice to somehow hide them... is it possible?), functions and
tables for internal use only...
Next step, let the configure process define pertinent macros...
Then, the hiding/aliasing game can start :-)
Regards,
m
--
http://bodrato.it/software/
_______________________________________________
gmp-devel mailing list
gmp-devel@gmplib.org
http://gmplib.org/mailman/listinfo/gmp-devel
