From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org, Decibel! <decibel@decibel.org>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Subject: Re: Code examples
Date: Tue, 04 Sep 2007 12:19:14 -0400
Message-ID: <26291.1188922754@sss.pgh.pa.us> (raw)
In-Reply-To: <20070904143640.GF6466@alvh.no-ip.org>
References: <162867790709021328i7771aa9jfe79268bccbf123d@mail.gmail.com>
<200709040229.29591.peter_e@gmx.net>
<6062.1188866394@sss.pgh.pa.us>
<200709041101.54641.peter_e@gmx.net>
<24261.1188915090@sss.pgh.pa.us>
<20070904143640.GF6466@alvh.no-ip.org>
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Maybe we could set things up so that there are actual files which are
> programatically preprocessed to SGML to be included in the docs? That
> way, the docs always reflect the actual file, which by itself is
> compilable. The SGML source would only contain something like
> <include file="examples/foo.c" /> or something like that.
Well, if we have actual contrib modules (which is still a good idea
so that they get tested on a regular basis), I don't see any need to
copy the code into the docs at all. The docs should just say "a working
example can be found in contrib/whatever".
regards, tom lane
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, peter_e@gmx.net, decibel@decibel.org, oleg@sai.msu.su, pavel.stehule@gmail.com
Subject: Re: Code examples
In-Reply-To: <26291.1188922754@sss.pgh.pa.us>
* 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