From: Dan Cross <crossd@gmail.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Marcus Clark <marcus.e.clark@outlook.com>, TUHS <TUHS@tuhs.org>
Subject: [TUHS] Re: Does anyone have any memories of using cscope that they care to share?
Date: Thu, 4 Apr 2024 18:41:15 -0400 [thread overview]
Message-ID: <CAEoi9W6dk-5yzetLpPpTKO2tYYFMhj3KOTKVP-3wSJ+sv5VHGw@mail.gmail.com> (raw)
In-Reply-To: <20240404223828.GD2235@mcvoy.com>
On Thu, Apr 4, 2024 at 6:38 PM Larry McVoy <lm@mcvoy.com> wrote:
> Interesting, no. Fond memories, absolutely. On SPARC machines with 4MB
> of ram, cscope was pretty essential if you wanted to get anything done.
> I used it a ton, made me way more productive.
That aspect of the culture remained and carried on to the descendents of Sun.
cscope is still very much used in the illumos project. In fact, I used
it yesterday (though not for illumos).
- Dan C.
> On Thu, Apr 04, 2024 at 09:16:31PM +0000, Marcus Clark wrote:
> >
> > 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.
>
> --
> ---
> Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2024-04-04 22:42 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 [this message]
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
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=CAEoi9W6dk-5yzetLpPpTKO2tYYFMhj3KOTKVP-3wSJ+sv5VHGw@mail.gmail.com \
--to=crossd@gmail.com \
--cc=TUHS@tuhs.org \
--cc=lm@mcvoy.com \
--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).