Re: Lines of code in PG 8.0 & 8.1? - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Lines of code in PG 8.0 & 8.1?
Date
Msg-id 200509231628.j8NGSrk02649@candle.pha.pa.us
Whole thread Raw
In response to Re: Lines of code in PG 8.0 & 8.1?  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-general
Jim C. Nasby wrote:
> Is there some reasonable way to get that to not include comments?

Not that I know of, but considering the complexity of our code, I _want_
to count comments.

---------------------------------------------------------------------------


>
> On Thu, Sep 22, 2005 at 06:04:55PM -0400, Bruce Momjian wrote:
> >
> > For 8.1beta2 I get:
> >
> >     684533
> >
> > and for 8.0.X I get:
> >
> >     648130
> >
> > I used:
> >
> >     # This script is used to compute the total number of "C" lines in the release
> >     # This should be run from the top of the CVS tree after a 'make distclean'
> >     find . -name '*.[chyl]' | xargs cat| wc -l
> >
> > I added this script to src/tools so we will have it for consistency.
> > This shows a 5% increase in code size from 8.0.X and 8.1.X, which is
> > consistent with previous releases, except for 8.0, which was a huge
> > jump.
> >
> > ---------------------------------------------------------------------------
> >
> > Rafael Martinez wrote:
> > -- Start of PGP signed section.
> > > Hello
> > >
> > > I am preparing a presentation about PostgreSQL and I need some help.
> > >
> > > I have found some information [1] about the lines of code the different
> > > versions (until 7.4) of PostgreSQL have, but I can not find numbers for
> > > version 8.0 and 8.1.
> > >
> > > This is what I have:
> > > 1996: 6.0 - 178K
> > > 1997: 6.[12] - 225K
> > > 1998: 6.[34] - 297K
> > > 1999: 6.5 - 331K
> > > 2000: 7.0 - 383K
> > > 2001: 7.1 - 410K
> > > 2002: 7.[23] - 453K
> > > 2003: 7.4 -  508K
> > >
> > > I could find out the numbers for 8.0 and 8.1 myself if I know the
> > > 'rules' used to find out the number of lines in the other versions. Has
> > > anyone this information?
> > >
> > > Thanks in advance.
> > >
> > > [1] http://candle.pha.pa.us/ - PostgreSQL: Past, Present, and Future
> > > (Bruce Momjian)
> > >
> > > --
> > > Rafael Martinez, <r.m.guerrero@usit.uio.no>
> > > Center for Information Technology Services
> > > University of Oslo, Norway
> > >
> > > PGP Public Key: http://folk.uio.no/rafael/
> > -- End of PGP section, PGP failed!
> >
> > --
> >   Bruce Momjian                        |  http://candle.pha.pa.us
> >   pgman@candle.pha.pa.us               |  (610) 359-1001
> >   +  If your life is a hard drive,     |  13 Roberts Road
> >   +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: don't forget to increase your free space map settings
> >
>
> --
> Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
> Pervasive Software      http://pervasive.com    work: 512-231-6117
> vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: SQL command to dump the contents of table failed: PQendcopy()
Next
From: Michael Fuhr
Date:
Subject: Re: SQL command to dump the contents of table failed: PQendcopy() failed. Error message from server: socket not open