From: law@redhat.com
To: Diego Novillo <dnovillo@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Thoughts on doxygen for internal documentation
Date: Thu, 16 Jan 2003 18:16:00 -0000 [thread overview]
Message-ID: <200301161753.h0GHrpt7009736@localhost.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 16 Jan 2003 12:34:37 EST." <20030116173437.GA2593@tornado.toronto.redhat.com>
In message <20030116173437.GA2593@tornado.toronto.redhat.com>, Diego Novillo wr
ites:
>On Thu, 16 Jan 2003, Jeff Law wrote:
>
>> Actually, I wouldn't go with doxygen stuff at all unless it's been
>> OK'd for the rest of the compiler proper.
>>
>Oh, well, OK. In reality all I we *really* need is to delimit
>comments with /** */. All the rest is up to doxygen to figure
>out. So, even if the comments are not delimited with /** */,
>doxygen is still useful.
>
>Let me rephrase the question then. Would it be OK to start
>documenting major functions and data structures with /** */
>instead of /* */?
Same answer. If /** is acceptable for the rest of the compiler
proper, then I'd go with it on tree-ssa. If it isn't acceptable,
then I would avoid it as it just makes more work for you. Yes, you
can find/change them with sed, but what's the point.
I'll note that /** is contrary to the GNU coding standards.
jeff
next prev parent reply other threads:[~2003-01-16 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 23:48 Diego Novillo
2003-01-16 10:47 ` Phil Edwards
2003-01-16 18:12 ` law
2003-01-16 18:14 ` Diego Novillo
2003-01-16 18:16 ` law [this message]
2003-01-16 18:18 ` Theodore Papadopoulo
2003-01-16 18:57 ` Gabriel Dos Reis
2003-01-16 19:11 ` law
2003-01-16 19:53 ` Andrew Haley
2003-01-16 23:36 ` Toon Moene
2003-01-16 19:18 ` Joel Sherrill
2003-01-16 19:35 ` Marc Espie
2003-01-16 19:37 ` Andrew Haley
2003-01-16 19:57 ` Theodore Papadopoulo
2003-01-17 0:26 ` Daniel Egger
2003-01-17 16:15 ` Daniel Berlin
2003-01-19 5:09 ` Daniel Egger
2003-01-16 18:20 ` Diego Novillo
2003-01-16 18:27 ` Gabriel Dos Reis
2003-01-16 18:29 ` law
2003-01-16 18:25 ` Daniel Berlin
2003-01-17 4:00 ` Kurt Wall
2003-01-16 20:03 ` Joseph S. Myers
2003-01-17 11:05 ` Tony Finch
2003-01-18 22:21 ` Daniel Egger
2003-01-18 16:17 Robert Dewar
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=200301161753.h0GHrpt7009736@localhost.redhat.com \
--to=law@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
/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
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 read-only IMAP folder(s) and NNTP newsgroup(s).