logo       

Assertions in CoordinateArraySequence: msg#00063

gis.geos.devel

Subject: Assertions in CoordinateArraySequence

CoordinateArraySequence has a number of assertions that check to see if the requested index is out of bounds of the array. If it is, then the assertion is thrown - at least in Debug mode.

I'd guess assertions are off in Release builds (haven't checked), so a segmentation fault would occur.

Could this be changed to exceptions? When playing around at the command line with Ruby or Python, its not very nice to have your application terminate because you specify an invalid index.

The reason I can see for not doing this is the extra overhead in checking the bounds - is that the case? If so, are there profiling results showing that it really is a big deal?

Thanks,

Charlie

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
geos-devel mailing list
geos-devel@xxxxxxxxxxxxxxxxxxxx
http://geos.refractions.net/mailman/listinfo/geos-devel
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise