I noticed the following error in the chapter on ECPG...

cbbrowne@dba2gsql-HEAD/doc/src/sgml> cvs diff -u ecpg.sgml
Index: ecpg.sgml
================================================== =================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.77
diff -c -u -r1.77 ecpg.sgml
cvs diff: conflicting specifications of output style
--- ecpg.sgml 23 Oct 2006 18:10:31 -0000 1.77
+++ ecpg.sgml 4 Dec 2006 15:32:16 -0000
@@ -4665,7 +4665,7 @@
</para>

<para>
- The preprocessed file can be compiled normally, for example:
+ The processed file can be compiled normally, for example:
<programlisting>
cc -c prog1.c
</programlisting>
--
let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];;
http://linuxdatabases.info/info/linuxxian.html
Developmental Psychology
"Schoolyard behavior resembles adult primate behavior because "Ontogeny
Recapitulates Phylogeny" doesn't stop at birth."
-- Mark Miller

The original looks more correct to me. After the file has been run
through the preprocessor, it becomes "preprocessed".

Chris Browne wrote:
> I noticed the following error in the chapter on ECPG...
>
> cbbrowne@dba2gsql-HEAD/doc/src/sgml> cvs diff -u ecpg.sgml
> Index: ecpg.sgml
> ================================================== =================
> RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v
> retrieving revision 1.77
> diff -c -u -r1.77 ecpg.sgml
> cvs diff: conflicting specifications of output style
> --- ecpg.sgml 23 Oct 2006 18:10:31 -0000 1.77
> +++ ecpg.sgml 4 Dec 2006 15:32:16 -0000
> @@ -4665,7 +4665,7 @@
> </para>
>
> <para>
> - The preprocessed file can be compiled normally, for example:
> + The processed file can be compiled normally, for example:
> <programlisting>
> cc -c prog1.c
> </programlisting>


--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

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

heikki@enterprisedb.com ("Heikki Linnakangas") writes:
> The original looks more correct to me. After the file has been run
> through the preprocessor, it becomes "preprocessed".

The other option I was thinking of was "postprocessed," because the .c
file comes *after* processing.
--
let name="cbbrowne" and tld="linuxdatabases.info" in String.concat "@" [name;tld];;
http://linuxdatabases.info/info/emacs.html
Rules of the Evil Overlord #221. "My force-field generators will be
located inside the shield they generate."
<http://www.eviloverlord.com/>

On Mon, Dec 04, 2006 at 10:33:47AM -0500, Chris Browne wrote:
> I noticed the following error in the chapter on ECPG...
> ...
> - The preprocessed file can be compiled normally, for example:
> + The processed file can be compiled normally, for example:

I beg to disagree. ECPG is an "embedded SQL preprocessor", so why can't
the file be called "preprocessed"?

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

On Mon, Dec 04, 2006 at 12:40:28PM -0500, Chris Browne wrote:
> The other option I was thinking of was "postprocessed," because the .c
> file comes *after* processing.

Well, the .c file is the one that should be processed. So you have to
preprocess the .pc file to get a .c file.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate