[geos-devel] const-correctness

[Martin Davis]

My personal opinion is that it's probably more trouble than it's worth, at this point.  As the FAQ points out it's a bear trying to retrofit const correctness.  

What sort of bugs was it catching?

Martin Davis, Senior Technical Architect
Vivid Solutions Inc.
Suite #1A-2328 Government Street   Victoria, B.C.   V8T 5G5
Phone: (250) 385 6040    Fax: (250) 385 6046



> -----Original Message-----
> From: strk [mailto:strk at keybit.net]
> Sent: Sunday, October 19, 2003 3:40 AM
> To: geos-devel at geos.refractions.net
> Subject: [geos-devel] const-correctness
> 
> 
> What do you think about getting things const correct in GEOS ?
> It helped a lot finding and fixing bugs so far, but it is still
> an incomplete work.
> 
> Quoting from C++ FAQ Lite:
> <http://www.parashift.com/c++-faq-lite/const-correctness.html#
faq-18.3>

[18.3] Should I try to get things const correct "sooner" or "later"?

   At the very, very, very beginning.

   Back-patching const correctness results in a snowball effect: every
   const you add "over here" requires four more to be added "over there."

--strk;

_______________________________________________
geos-devel mailing list
geos-devel at geos.refractions.net
http://geos.refractions.net/mailman/listinfo/geos-devel