#202: Undefined behavior in Coordinate::hashCode
+---
Reporter: mloskot |Owner: geos-devel@lists.osgeo.org
Type: defect | Status: new
Priority: m
#202: Undefined behavior in Coordinate::hashCode
+---
Reporter: mloskot |Owner: geos-devel@lists.osgeo.org
Type: defect | Status: new
Priority: m
#202: Undefined behavior in Coordinate::hashCode
+---
Reporter: mloskot |Owner: geos-devel@lists.osgeo.org
Type: defect | Status: new
Priority: m
Howard Butler wrote:
On Aug 29, 2008, at 11:03 AM, Charlie Savage wrote:
+1 for spaces on my side. And just to really stir things up, I'd go
for an indentation of 2 spaces
I think it is an OSGeo standard for all source code to be spaces with an
indentation level of 4 spaces :)
Hobu,
Howard Butler wrote:
>
> On Aug 29, 2008, at 10:42 AM, Mateusz Loskot wrote:
>
>> Sean Gillies wrote:
>>> I'm finding a lot of tabs in the GEOS source -- is this our convention?
>>
>> Sean,
>>
>> AFAIR, Sandro preferred to use tabs. I've also found it inconvenient
>> as I personally believe in sp
On Aug 29, 2008, at 11:03 AM, Charlie Savage wrote:
+1 for spaces on my side. And just to really stir things up, I'd go
for an indentation of 2 spaces
I think it is an OSGeo standard for all source code to be spaces with
an indentation level of 4 spaces :) We don't want to jeopardize
I'm finding a lot of tabs in the GEOS source -- is this our convention?
Trying to start a religious war, eh?
+1 for spaces on my side. And just to really stir things up, I'd go for
an indentation of 2 spaces
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
___
On Aug 29, 2008, at 10:42 AM, Mateusz Loskot wrote:
Sean Gillies wrote:
I'm finding a lot of tabs in the GEOS source -- is this our
convention?
Sean,
AFAIR, Sandro preferred to use tabs. I've also found it inconvenient
as I personally believe in spaces :-)
Perhaps, if others will agree
Sean Gillies wrote:
I'm finding a lot of tabs in the GEOS source -- is this our convention?
Sean,
AFAIR, Sandro preferred to use tabs. I've also found it inconvenient as
I personally believe in spaces :-)
Perhaps, if others will agree, we can migrate GEOS sources to spaces.
Single big batch
I'm finding a lot of tabs in the GEOS source -- is this our convention?
Sean
___
geos-devel mailing list
geos-devel@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geos-devel
Ben Harper wrote:
Apologies for sending this to the entire list, but I couldn't figure
out how to comment on the ticket alone. I created an OSGeo user
account, and logged in to trac, but still no GUI available.
Ben,
This is strange. Perhaps you could report this problem to SAC
mailing list: ht
Apologies for sending this to the entire list, but I couldn't figure out how to
comment on the ticket alone.
I created an OSGeo user account, and logged in to trac, but still no GUI
available.
Anyway, concerning an I32 hash on a double, I think the easiest naive solution
that does not have terri
12 matches
Mail list logo
