help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Peter Bray <pdb_ml@yahoo.com.au>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mdocml [CVS_2015_11_07] C++ Declaration Guards
Date: Sat, 7 Nov 2015 15:06:30 +0100	[thread overview]
Message-ID: <20151107140630.GD10393@athene.usta.de> (raw)
In-Reply-To: <563D700F.9090001@yahoo.com.au>

Hi Peter,

Peter Bray wrote on Sat, Nov 07, 2015 at 02:29:19PM +1100:

> I'll leave it to the developers and maintainers to choose the
> appropriate solution for their code base.

I just deleted them: KISS.

They have never been used for anything in more than six years
and are apparently becoming a portability headache.

Besides, i want to strongly discourage any use of C++ in
software documentation.  Getting away from C++ is one of the
chief design goals of the mandoc project.

 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2015-11-07 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07  3:29 Peter Bray
2015-11-07  3:37 ` Guy Harris
2015-11-07 14:06 ` Ingo Schwarze [this message]
2015-11-07 14:25   ` Joerg Sonnenberger
2015-11-07 14:34     ` Ingo Schwarze
2015-11-07 14:37       ` Joerg Sonnenberger
2015-11-11 10:57     ` Steffen Nurpmeso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151107140630.GD10393@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    --cc=pdb_ml@yahoo.com.au \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 NNTP newsgroup(s).