RE: [HACKERS] Re: CODE ANALYSIS FOR (an apparent error in answer from "##" (closest proximity)operator)

I'd like to keep track of any changes you make so I can keep the JDBC
Geometric classes in sync.

--
Peter T Mount, peter@maidstone.gov.uk, peter@retep.org.uk
Please note that this is from my works email. If you reply, please cc my
home address.

-----Original Message-----
From: owner-pgsql-hackers@hub.org [mailto:owner-pgsql-hackers@hub.org]On
Behalf Of Thomas G. Lockhart
Sent: Friday, May 01, 1998 3:22 AM
To: Gautam H Thaker
Cc: Postgres Hackers List
Subject: [HACKERS] Re: CODE ANALYSIS FOR (an apparent error in answer
from "##" (closest proximity)operator)

OK, I will try to work on this and provide you tested code.
(Since this is my first attempt to code in Postgres
it might take me a while though I have hacked for many
years overall.)

No problem.

Lines are more useful to me than lsegs. Is it easy
enough to add these input/output routines so that I can
continue to move forward prior to V6.4?

Yes. I'm starting to do that now, and we can coordinate patches. We may
as well copy the hackers list on at least our planning e-mails...

- Tom