From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Exploring a code base? Date: Sat, 07 Nov 2020 15:56:50 +0200 Message-ID: <83d00p6zj1.fsf@gnu.org> References: <57dcdf06-3bf4-4281-88d9-0e9c46adc757@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30900"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Nov 07 14:57:25 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kbOia-0007vr-I2 for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 07 Nov 2020 14:57:24 +0100 Original-Received: from localhost ([::1]:34356 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbOiZ-0002Lg-IK for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 07 Nov 2020 08:57:23 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34744) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kbOi2-0002LP-Uy for help-gnu-emacs@gnu.org; Sat, 07 Nov 2020 08:56:50 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58982) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kbOi2-00016e-MW for help-gnu-emacs@gnu.org; Sat, 07 Nov 2020 08:56:50 -0500 Original-Received: from [176.228.60.248] (port=2377 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kbOi1-00061R-Lr for help-gnu-emacs@gnu.org; Sat, 07 Nov 2020 08:56:50 -0500 In-Reply-To: (message from Yuri Khan on Sat, 7 Nov 2020 20:26:16 +0700) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:125089 Archived-At: > From: Yuri Khan > Date: Sat, 7 Nov 2020 20:26:16 +0700 > Cc: help-gnu-emacs > > Yeah, there exist many tools that attempt to take in the whole project > and generate a complete call graph. In my experience, most of the > time, for any project more complex than Hello World, the resulting > graph is too messy to be helpful. > > For one thing, I am not interested in all calls, only those through > which a particular data type flows as an argument or [part of] the > return value. This subgraph is smaller and simpler, and actually has a > chance to embed into a plane without many edge intersections. Maybe you could step back and describe in a bit more detail what kind of workflow you are trying to support, and how that contributes to the kind of code-base exploring job you have in mind. I do this quite a lot, and IME a combination of M-. and M-? (with the latter using the back-end of ID Utils, if possible) is entirely adequate. In particular, I don't think I ever was in the need of some graph to refactor a data type, I only needed to examine its uses. Basically, I'm asking why having a flat list of all the users of a data type, and reading the code of all of them, is not enough for this kind of job? What am I missing?