pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Otto A. Hirr, Jr. <otto.hirr@olabinc.com>
To: pgsql-hackers@postgresql.org
To: pgsql-interfaces@postgresql.org
Subject: Newbe hacker, interface question on includes...
Date: Mon, 22 Jan 2001 21:44:30 -0800
Message-ID: <000001c084ff$8fc5b680$7bf7663f@xcdt.olabinc.com> (raw)


I have begun perusing the source, eventually hoping to
contribute to the development effort.  I have noticed that
long ago the include files for a "component" were in the
component directory, eg src/backend/catalog/Attic/catalog.h,v
(here I'm assuming that Attic means a storage place for
items that use to be there but are no longer there...)
and now this file resides in src/include/catalog/catalog.h,v.  A quick
scan seems that this was a common transformation.

This seems to be a mighty step backwards, especially if
one considers the recommendations on large systems development
where you want to minimize dependancies...

Could someone point out the history of code relocation and rationale.

Thanks for any pointers.

Best regards,

.. Otto

Otto Hirr
OLAB Inc.
otto.hirr@olabinc.com
503 / 617-6595




view thread (2+ messages)  latest in thread

Message-ID: <000001c084ff$8fc5b680$7bf7663f@xcdt.olabinc.com>
Permalink:  ../000001c084ff$8fc5b680$7bf7663f@xcdt.olabinc.com/
Also on:    postgresql.org/message-id/000001c084ff$8fc5b680$7bf7663f@xcdt.olabinc.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: otto.hirr@olabinc.com, pgsql-hackers@postgresql.org
  Subject: Re: Newbe hacker, interface question on includes...
  In-Reply-To: <000001c084ff$8fc5b680$7bf7663f@xcdt.olabinc.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox