public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: EMPEROR <kalyan_ch@gdit.iiit.net>
To: "Rajasekaran, Deepak (IE10)" <Rajasekaran.Deepak@honeywell.com>
Cc: GCC Help <gcc-help@gcc.gnu.org>
Subject: Re: Can GCC be used for extracting comments (like Doxygen)?
Date: Mon, 03 Oct 2005 11:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0510031629160.28710@students.iiit.net> (raw)
In-Reply-To: <77ED2BF75D59D1439F90412CC5B1097425985AAC@ie10-sahara.hiso.honeywell.com>

hi
u may find this useful.
Doxygen is a documentation system for C++, C, Java, Objective-C, Python, 
IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.

http://www.stack.nl/~dimitri/doxygen/



On Mon, 3 Oct 2005, Rajasekaran, Deepak (IE10) wrote:

> I have many C files with Javadoc-style comments. Each statement contains a
> comment before it. I need to generate documentation from this. I am looking
> for a tool which takes the C files and generates a file from which the
> documentation and the corresponding source code can be easily extracted
> (i.e., more easily than by parsing the source code).
>
> I tried Ccdoc but it processes only header files. I tried Doxygen but it
> loses the correspondence between the comments and source code. Is it
> possible to use GCC for this purpose?
>
> Thanks in advance.
>

-- 

 	Both Optimists and pessimists contribute equally to the society
 		Optimists invent aeroplanes and pessimists, parachutes

      reply	other threads:[~2005-10-03 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 10:35 Rajasekaran, Deepak (IE10)
2005-10-03 11:00 ` EMPEROR [this message]

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=Pine.LNX.4.61.0510031629160.28710@students.iiit.net \
    --to=kalyan_ch@gdit.iiit.net \
    --cc=Rajasekaran.Deepak@honeywell.com \
    --cc=gcc-help@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).