|
Re: Assertions in CoordinateArraySequence: msg#00082gis.geos.devel
Sure. But this is a different use case then a C/C++ client. It is programmers working with GEOS from Ruby/Python. In both languages array/vetor/list indices are checked and exceptions are raised if they are out of bounds. If we want geos to fit in well in these environments, then it would make sense for GEOS to behave the same way. Also, I don't think there is anything in either language that you can do (not including bugs of course or a call to abort) that would cause your session to abort. Anyway - don't know why this did not dawnd on me before - but let's do this. I'll add in the checks in the wrapper since CoordinateSequence provides a size method. That way the api can stay the same but we can get bounds checkings for Ruby/Python. Charlie
geos-devel mailing list geos-devel@xxxxxxxxxxxxxxxxxxxx http://geos.refractions.net/mailman/listinfo/geos-devel |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Assertions in CoordinateArraySequence: 00082, Mateusz Loskot |
|---|---|
| Next by Date: | Re: Assertions in CoordinateArraySequence: 00082, strk |
| Previous by Thread: | Re: Assertions in CoordinateArraySequencei: 00082, strk |
| Next by Thread: | Re: Assertions in CoordinateArraySequence: 00082, strk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |