[postgis-devel] iscachable

[strk at refractions.net]

Ok, here are my defines:

#if USE_VERSION > 72
# define _IMMUTABLE_STRICT IMMUTABLE STRICT
# define _IMMUTABLE IMMUTABLE
# define _STABLE_STRICT STABLE STRICT
# define _STABLE STABLE
# define _VOLATILE_STRICT VOLATILE STRICT
# define _VOLATILE VOLATILE
# define _STRICT STRICT
#else // USE_VERSION <= 72
# define _IMMUTABLE_STRICT  with(iscachable,isstrict)
# define _IMMUTABLE with(iscachable)
# define _STABLE_STRICT with(isstrict)
# define _STABLE
# define _VOLATILE_STRICT with(isstrict)
# define _VOLATILE
# define _STRICT with(isstrict)
#endif // USE_VERSION <= 72

Note that _STABLE and _VOLATILE leave default behaviour for PG<73.
Do they sound correct to everybody ?
--strk;

On Fri, Jan 14, 2005 at 04:17:23PM +0100, Markus Schaber wrote:
> Hi, strk,
> 
> strk at refractions.net schrieb:
> 
> > Note that we could use STABLE  for PG>72 with a preprocessor
> > switch..
> 
> I think this is a good idea so PG73+ optimizers can take advantage of
> STABLE.
> 
> Markus



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


-- 

For standing up against patentability of software,

  Thank You, Poland!

Read the intervention:    http://kwiki.ffii.org/ConsPolon041221En
Send your thanks:         thankyoupoland.info
Read/do more:		  http://www.noepatents.org/