I am also usually working with a simple editor and command line, but because the postgresql project is too big for a person who is looking at the source 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 look at is easy.

Anyway, CDT's opening definition feature did not work for postgresql source. I do not know why. I just wanted to know if somebody had accomplished this.

Regards,

dakotali


----- Original Message ----
From: Andrew Dunstan <andrew@dunslane.net>
To: Chris Browne<cbbrowne@acm.org>
Cc: pgsql-hackers@postgresql.org
Sent: Sunday, December 17, 2006 5:21:33 PM
Subject: Re: [HACKERS] development environment of postgres

Chris Browne wrote:
> dakotalidavid@yahoo.com (dakotali kasap) writes:
>> I want to ask, which development environment should I use to add new
>> features to postgresql. Is Eclipse CDT (C/C++ DevelopmentTool)
>> suitable for this, or are you using another environment, or just
>> using pico, vi, etc.?
>
> I can't speak for you. I find my competence is maximized when I'm
> using Emacs; others find other sets of tools preferable. The code
> doesn't care what tool you're best with.
>
> - There are people who will swear by vi + ctags.
>
> - There are some who still use QED. (Albeit not for this project...)
> <http://cm.bell-labs.com/cm/cs/who/dmr/qed.html>
> (These would be extreme Unix partisans who think that the move from
> ed to vi was a Bad Thing... :-))
>
> - Others prefer some form of Emacs.
>
> - One of my coworkersI think uses pico for most things; he's not keen
> on either of the typical Unix editors.
>

Higher end IDEs tend to work best with some sort of project setup. If we
were to support that it would be impossible -we'd forever have breakage.
We support exactly the toolset needed to build postgres, and let you
choose your own creation and management tools.

There are plenty of emacs users among the hackers, and it's possible to
set up emacs to drive building, debugging, the whole thing. For the most
part I just use its editing facities, and drive everything else from the
command line.

cheers

andrew


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster






__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

dakotali kasap <dakotalidavid@yahoo.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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Hi,

To modify postgres, i use kwrite... then "make and make install".... that's
all....

But i use this web site to navegate inside the postgres code, i found it
very useful....
http://www.mcknight.de/pgsql-doxygen/cvshead/html/

(of course, this web site may be don't have the recent realease of postgres)

On 12/17/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> dakotali kasap <dakotalidavid@yahoo.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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>