linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: soraberri <421246@posta.unizar.es>
To: linux-c-programming@vger.kernel.org
Subject: Re: development tools for interpreting code
Date: Tue, 21 Dec 2004 19:48:17 +0100	[thread overview]
Message-ID: <cq9r6n$5nd$2@sea.gmane.org> (raw)
In-Reply-To: <cq9icd$cpa$1@sea.gmane.org>

soraberri wrote:
> Hi all,
> 
> In this stage of my learning I am basically trying to understand some 
> code that others have develop. The code is about bluetooth tools but 
> this is unrelevant at this moment. Rigth now I'm using Kdevelop for this 
> task with the source that I want to understand loaded into a new 
> project, and I always find the same problem which I will describe you in 
> terms of an example:
> 
> at some point of the code I find a call to a function or a typedef name 
> (for exmple str2ba) and I would like to find the header file or even the 
> source file where this function (or type) is defined. I can only use the 
> Grep:str2ba command found under "Find in files..." dialog but sometimes 
> this is not suitable because I have to tell manually the path from the 
> starting point of the search, and if I don't know exactly the rigth 
> folder, the number of results searched can be too many for examining. I 
> guess it may be a better way, since the program compiles and has the 
> appropiate includes (#include <header>), so the compiler must know where 
> the function is defined.
> 
> So, every suggestions would be wellcome,
> 
> thaks in advance
> 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Thank you for all your help. I'll study a bit all these choices and will 
try out. very helpful posts!


  parent reply	other threads:[~2004-12-21 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 16:17 development tools for interpreting code soraberri
2004-12-21 16:35 ` Nir Dremer
2004-12-21 16:53   ` soraberri
2004-12-21 17:02     ` Nir Dremer
2004-12-21 17:38       ` José Ricardo
2004-12-21 18:45       ` soraberri
2004-12-21 18:08 ` Jan-Benedict Glaw
2004-12-21 18:48 ` soraberri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-21 18:39 Huber, George K RDECOM CERDEC STCD SRI

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='cq9r6n$5nd$2@sea.gmane.org' \
    --to=421246@posta.unizar.es \
    --cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).