Hi Tor, *,
On Mon, Aug 8, 2011 at 9:28 AM, Tor Lillqvist <tlillqvist@novell.com> wrote:
If one of us (cloph) strongly feels that we should use # comments in configure.in and not dnl
comments (well, keywords), and most others (?) (including me) are indifferent, why don't just
change them all in one go then?
I don't feel /that/ strongly about it. But if configure.in is touched,
I indeed would prefer it to be changed in the touched part, and not
introduced for new stuff.
I wonder if there is some cases where the dnl keyword can not just be changed to # without
changing the semantics of the autoconf/shell code?
The "section headings" are enough to have in the generated configure,
and those are safe to change to #.
ciao
Christian
Context
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.