Re: Is the lcl_LocalFunction naming convention useful?

Stephan Bergmann <sbergman -AT- redhat.com>
Mon, 15 Oct 2012 12:24:38 +0200

On 10/09/2012 07:59 AM, Tor Lillqvist wrote:

Where did this lcl_ convention come from? The lcl_ prefix has no
meaning to a compiler or linker.

One way this /did/ have influence on linking was the old mechanism toselect symbols for DLL export on Windows, where the available symbolswere matched against white/black-lists, and lcl_* was alwaysblack-listed. Long gone (and I have no idea why people didn't simplyuse "static" anyway).


Stephan

Context

Is the lcl_LocalFunction naming convention useful? · Tor Lillqvist
- Re: Is the lcl_LocalFunction naming convention useful? · Miklos Vajna
  - Re: Is the lcl_LocalFunction naming convention useful? · Tor Lillqvist
    - Re: Is the lcl_LocalFunction naming convention useful? · Miklos Vajna
      - Re: Is the lcl_LocalFunction naming convention useful? · Lubos Lunak
    - Re: Is the lcl_LocalFunction naming convention useful? · Michael Meeks
- Re: Is the lcl_LocalFunction naming convention useful? · Noel Grandin
- Re: Is the lcl_LocalFunction naming convention useful? · Bjoern Michaelsen
- Re: Is the lcl_LocalFunction naming convention useful? · Lubos Lunak
- Re: Is the lcl_LocalFunction naming convention useful? · Kohei Yoshida
- Re: Is the lcl_LocalFunction naming convention useful? · Stephan Bergmann
  - Re: Is the lcl_LocalFunction naming convention useful? · Eike Rathke

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.