* libc_hidden_* for public functions
@ 2017-10-04 23:21 Ilya Skapenko
2017-10-05 3:24 ` Carlos O'Donell
0 siblings, 1 reply; 2+ messages in thread
From: Ilya Skapenko @ 2017-10-04 23:21 UTC (permalink / raw)
To: libc-help
Hello!
Please, help me to understand, why and when do you use macroses like
libc_hidden_(proto, def)?
As I understood, you use them, when using this symbol by library itself.
But you could do it without these macroses, what's the purpose of them?
What for do they create __GI_*function_name* alias for function?
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: libc_hidden_* for public functions
2017-10-04 23:21 libc_hidden_* for public functions Ilya Skapenko
@ 2017-10-05 3:24 ` Carlos O'Donell
0 siblings, 0 replies; 2+ messages in thread
From: Carlos O'Donell @ 2017-10-05 3:24 UTC (permalink / raw)
To: Ilya Skapenko, libc-help
On 10/04/2017 04:21 PM, Ilya Skapenko wrote:
> Hello!
> Please, help me to understand, why and when do you use macroses like
> libc_hidden_(proto, def)?
> As I understood, you use them, when using this symbol by library itself.
> But you could do it without these macroses, what's the purpose of them?
> What for do they create __GI_*function_name* alias for function?
https://sourceware.org/glibc/wiki/Style_and_Conventions#Double-underscore_names_for_public_API_functions
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-05 3:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-10-04 23:21 libc_hidden_* for public functions Ilya Skapenko
2017-10-05 3:24 ` Carlos O'Donell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).