The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <brad@anduin.eldar.org>
To: Marcus Clark <marcus.e.clark@outlook.com>
Cc: TUHS@tuhs.org
Subject: [TUHS] Re: Does anyone have any memories of using cscope that they care to share?
Date: Fri, 05 Apr 2024 02:48:37 -0400	[thread overview]
Message-ID: <xonwmpce24a.fsf@anduin.eldar.org> (raw)
In-Reply-To: <LO2P123MB74066CA4C75C4E6FF10DA007D53C2@LO2P123MB7406.GBRP123.PROD.OUTLOOK.COM> (message from Marcus Clark on Thu, 4 Apr 2024 21:16:31 +0000)


Marcus Clark <marcus.e.clark@outlook.com> writes:

> Wikipedia has a brief page on cscope, which has a link  to
> https://cscope.sourceforge.net/history.html
> written by Harold Bamford, in which he talks about the
> early days of cscope at Bell Labs and its inventor Joe Steffan.
>
> I wondered if anyone can add any interesting information about using
> cscope on their projects or anything about its development.
>
> -Marcus.


A long time ago on the project I was on when I was at AT&T / Lucent, the
department I was in had a wrapper shell script around cscope.  We used
this wrapper to query the source of the product that we worked on.  The
source, at the time, was huge and cscope was about the only thing around
that let you search the source with the least amount of pain.  The
wrapper script simply invoked cscope in a safe way that kept it from
accidently re-indexing the source code when the developer didn't mean to
do that.  We did re-indexes in a cron job every once in a while.

Since the source to cscope is available now, it has made it into pkgsrc
and I use it on the NetBSD source tree all of the time.




-- 
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org

  parent reply	other threads:[~2024-04-05  6:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 21:16 [TUHS] " Marcus Clark
2024-04-04 22:38 ` [TUHS] " Larry McVoy
2024-04-04 22:41   ` Dan Cross
2024-04-04 23:35   ` Greg 'groggy' Lehey
2024-04-05  1:37     ` Dave Horsfall
2024-04-05  2:07       ` Larry McVoy
2024-04-05  3:54         ` Greg 'groggy' Lehey
2024-04-05  4:03           ` G. Branden Robinson
2024-04-07 21:39           ` Dave Horsfall
2024-04-05  1:38 ` Noel Hunt
2024-04-05 10:11   ` Ralph Corderoy
2024-04-05 20:46     ` Noel Hunt
2024-04-05  6:48 ` Brad Spencer [this message]
2024-04-06  5:48 ` Kevin Bowling

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=xonwmpce24a.fsf@anduin.eldar.org \
    --to=brad@anduin.eldar.org \
    --cc=TUHS@tuhs.org \
    --cc=marcus.e.clark@outlook.com \
    /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).