public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Tatsuo Ishii <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Subject: Re: documentation structure
Date: Fri, 19 Jul 2024 12:22:14 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwZhikLAfG9ntU-611adW0AnnPFJ_wx7Hy3Lb_v7M7x27Q@mail.gmail.com>
References: <CACJufxH+Yi521QrncwnW4sFGOhPmJQpsmoJ+Ynj+VpHu5wAahQ@mail.gmail.com>
	<CADkLM=cXvybjLKQ+n3=kwFLyRp6AA9VPh_0QJvWBU2tZFmxN-g@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAKFQuwZhikLAfG9ntU-611adW0AnnPFJ_wx7Hy3Lb_v7M7x27Q@mail.gmail.com>

"David G. Johnston" <[email protected]> writes:
> On Thu, Jul 18, 2024 at 8:06 PM Tatsuo Ishii <[email protected]> wrote:
>>> I'm opposed to having a separate file for every function. I think
>>> breaking up func.sgml into one piece per sect1 is about right.

>> That will create at least 30 func-xx.sgml files.
>> I am afraid that's too many?

> The premise and the resultant number of files both seem reasonable to me.

I agree.  The hundreds that would result from file-per-function, or
anything close to that, would be too many.  But I can deal with
file-per-sect1.  For context, I count currently 167 sgml/*.sgml files
plus 219 ref/*.sgml, so adding 30 more would be an 8% increase.

Do we want to use a "func-" prefix on the file names?  I could
imagine dispensing with that as unnecessary; or another idea
could be to make a new subdirectory func/ for these.

			regards, tom lane

view thread (5+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: documentation structure
  In-Reply-To: <[email protected]>

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

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