<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38">
<TITLE>RE: shapelib fixes ?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Sandro,<BR>
<BR>
Good point. I was thinking of whether it would be better to just change<BR>
the DBFReadDeleted in shp2pgsql to !DBFReadDeleted, but given the verbiage<BR>
it seemed more confusing to do that. Then again I hate the function name altogether. I think I spent more time figuring out what the hell does that mean than doing anything. I would prefer IsDBFRecordDeleted.<BR>
<BR>
It seems to me DBFReadDeleted is asking the question, is the record we are reading deleted (or is it if the record is Delete then don't read it, but its reading it to figure out it is deleted). It took me a while to figure out what that meant? Or at least that is what that phrase means to me. I think IsDBFRecordDeleted or IsDBFRecordActive is clearer. <BR>
<BR>
Also I'm not sure this is not Paul's concoction because comparing to the dbfopen from the 1.3.3, this function isn't even there. I don't have access to Frank's shapelib so can't commit changes.<BR>
<BR>
Paul you didn't happen to commit this change to shapelib did you or synch from there to get this function?<BR>
<BR>
Thanks,<BR>
Regina<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: strk [<A HREF="mailto:strk@keybit.net">mailto:strk@keybit.net</A>]<BR>
Sent: Thu 1/22/2009 12:47 PM<BR>
To: Obe, Regina<BR>
Cc: postgis-devel@postgis.refractions.net<BR>
Subject: shapelib fixes ?<BR>
<BR>
Salve Regina!<BR>
<BR>
I noticed this commit:<BR>
<BR>
* r3561 /trunk/loader/dbfopen.c: Fix DBFReadDeleted logic<BR>
-- should return 1 if record is deleted and 0 if it is not<BR>
deleted<BR>
<BR>
Note that dbfopen.c is part of Frank Warmerdam's<BR>
shapelib, copied in postgis tree verbatim and occasionally<BR>
updated to new versions.<BR>
This means that on next update your "fix" would be reverted<BR>
(unless it is in upstream, which I strongly dubt).<BR>
<BR>
Generally, returning 0 for success and 1 for error is a trick<BR>
to allow for fine-grained error reporting. A success is<BR>
a success, while an error can be for different reasons, thus<BR>
the non-zero return on error.<BR>
<BR>
--strk;<BR>
<BR>
Free GIS & Flash consultant/developer () ASCII Ribbon Campaign<BR>
<A HREF="http://foo.keybit.net/~strk/services.html">http://foo.keybit.net/~strk/services.html</A> /\ Keep it simple!<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>