From: Joerg Sonnenberger <email@example.com> To: firstname.lastname@example.org Subject: Re: mdocml [CVS_2015_11_07] C++ Declaration Guards Date: Sat, 7 Nov 2015 15:37:53 +0100 [thread overview] Message-ID: <20151107143753.GA17696@britannica.bec.de> (raw) In-Reply-To: <20151107143449.GF10393@athene.usta.de> On Sat, Nov 07, 2015 at 03:34:49PM +0100, Ingo Schwarze wrote: > Hi Joerg, > > Joerg Sonnenberger wrote on Sat, Nov 07, 2015 at 03:25:23PM +0100: > > On Sat, Nov 07, 2015 at 03:06:30PM +0100, Ingo Schwarze wrote: > > >> 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. > > > Seriously, please don't call groff C++. It is not. It is C with classes. > > It doesn't even use the most fundamental data types like vectors. > > You have a point. > > Fortunately, INSTALL doen't talk about groff at all, > it only talks about mandoc design goals: > > One of the chief design goals of the mandoc toolbox is to make > sure that nothing related to documentation requires C++. > Consequently, linking mandoc against any kind of C++ program > would defeat the purpose and is not supported. > > So, i don't think i need to change anything there. Keep in mind that the purpose of the guards was the *inverse*. They make it simpler to *use* mandoc from C++ programs. Joerg -- To unsubscribe send an email to email@example.com
next prev parent reply other threads:[~2015-11-07 14:37 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 2015-11-07 14:25 ` Joerg Sonnenberger 2015-11-07 14:34 ` Ingo Schwarze 2015-11-07 14:37 ` Joerg Sonnenberger [this message] 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: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20151107143753.GA17696@britannica.bec.de \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: mdocml [CVS_2015_11_07] C++ Declaration Guards' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
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).