Re: New Defects reported by Coverity Scan for PostgreSQL - Mailing list pgsql-hackers

From Emre Hasegeli
Subject Re: New Defects reported by Coverity Scan for PostgreSQL
Date
Msg-id CAE2gYzw6iD1YTZ+67hA=s3AG5sbLCsGkHRYQ_Z1Kd+vhiM7ecA@mail.gmail.com
Whole thread Raw
In response to Re: New Defects reported by Coverity Scan for PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: New Defects reported by Coverity Scan for PostgreSQL
List pgsql-hackers
> Or perhaps I have it backwards and "l1" and "l2" need to be swapped in
> that description.  But the mere fact that there is any question about
> that means that the function is poorly documented and perhaps poorly
> named as well.  For that matter, is there a good reason why l1/l2
> have those roles and not the reverse?

Consistency.  I organized all xxx_closept_yyy(Point *result, xxx *l1,
yyy *l2) functions in a way that they find the find the point on "l1".


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: New Defects reported by Coverity Scan for PostgreSQL
Next
From: Sergei Kornilov
Date:
Subject: Re: Online enabling of checksums