From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | dakotali kasap <dakotalidavid(at)yahoo(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: development environment of postgres |
Date: | 2006-12-17 18:22:37 |
Message-ID: | 17112.1166379757@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
dakotali kasap <dakotalidavid(at)yahoo(dot)com> writes:
> --0-1517433147-1166375569=:82897
> Content-Type: text/plain; charset=ascii
> Content-Transfer-Encoding: quoted-printable
> I am also usually working with a simple editor and command line, but becaus=
> e the postgresql project is too big for a person who is looking at the sour=
> ce code for the first time, I thought it will be simpler using a tool like =
> CDT, because jumping directly to a function definition that he wants to loo=
> k at is easy.
That's an essential tool even for someone who knows the code well
... but you shouldn't think that there's only one way to do it.
I like glimpse under emacs (easily finds references to symbols as well
as their definitions; not specific to any one programming language).
I think some other people use ctags.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-12-17 18:38:50 | Re: [PATCHES] psql commandline conninfo |
Previous Message | dakotali kasap | 2006-12-17 17:12:49 | Re: development environment of postgres |