[postgis-devel]Use ofdeprecated functionsin non-deprecatedfunctions

[Obe, Regina]

>Yes, your example would spit out a notice for every call to Area(), and 
>yes, it would make things very slow, filling the logs, etc.  But, to me, 
>this would be a preferable first step to simply removing Area() and 
>break old apps cold.

>I have no idea if we even want to remove the deprecated functions in the 
>future (I thought there was talk on this earlier, but I can't seem to 
>find it).  If we remove deprecated functions, it will break old apps and 
>we would undoubtedly have to create a "restore_depreacted_functions" 
>script so folks can upgrade to the latest PostGIS version and still use 
>their old apps.  In which case, why would we even deprecate these 
>functions in the first place.  Or maybe, for PostGIS, "deprecate" simply 
>means "undocumented".

>-- Kevin

Personally I rarely look at notices and I think the people that would really benefit
from looking at them wouldn't.  I would much prefer things just break rather
than things silently work slow and fill up logs.  It would seem a little early to remove those functions just now, but I would think in 1-2 years we should.

Breaking is an obvious confirmation you are doing something wrong.  Slow is opaque and hard to troubleshoot. 
Rather than throw a notice we should just throw an error at that point with a 

"If you get this error - you should either upgrade or install the restore_deprecated_functions."

Just my two cents,
Regina
 


-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20080729/89937e4a/attachment.html>