Is the lcl_LocalFunction naming convention useful?
erack at redhat.com
Mon Oct 22 07:52:56 PDT 2012
On Monday, 2012-10-15 12:24:38 +0200, Stephan Bergmann wrote:
> symbols were matched against white/black-lists, and lcl_* was always
> black-listed. Long gone (and I have no idea why people didn't
> simply use "static" anyway).
IIRC, by chance, not using static stems from times where there was
a sort of code coverage run to reorder object files within libraries for
better paging, there static functions interrupted the call chain.
LibreOffice Calc developer. Number formatter stricken i18n transpositionizer.
GnuPG key 0x293C05FD : 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
Support the FSFE, care about Free Software! https://fsfe.org/support/?erack
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
More information about the LibreOffice