Re: export & public

new topic     » goto parent     » topic index » view thread      » older message » newer message
mattlewis said...

Enter the export scope. This declares symbols that cannot be propagated through additional include statements. So a library author could have internal library implementation that would remain hidden to the consumer of his library, but could be visible to multiple files within his library.

Might either of the words "private" or "restrict" better communicate the intention of the word "export"?

Export means "to send an item out from", without implying any innate restriction as to where the item might end up at, which seems to not be what is intended by using it in V4.0

"private" and "restrict" both seem to fairly clearly indicate that a symbol referenced by them is only available for use by the file that included the file containing the symbol.

Dan

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu