Optional new names for Mapscript classes

tbonfort commented 12 years ago

Reporter: sgillies@frii.com Date: 2004/03/05 - 17:10

Am going to support an experimental change in Mapscript class names 
that is controlled with a preprocessor symbol NEXT_GENERATION_CLASSES.

Will use it like

  swig -python -shadow -DNEXT_GENERATION_CLASSES mapscript.i

And if the symbol is defined we will rename

  layeroObj -> Layer
  mapObj -> Map

et cetera.

I'll also write a new layerObj.getShape method that is like the PHP-Mapscript
method which will be used if we've defined NEXT_GENERATION_CLASSES.

Nothing else changes so it won't break compatibility with the general SWIG
documentation.

tbonfort commented 12 years ago

Author: sgillies@frii.com Date: 2004/03/05 - 23:04

Have added directives in mapscript.i that do the renaming.  New test cases
for the next generation classes pass.

tbonfort commented 12 years ago

Author: sgillies@frii.com Date: 2004/03/06 - 18:10

This feature is now controlled by the NEXT_GENERATION_NAMES symbol.

tbonfort commented 12 years ago

Author: sgillies@frii.com Date: 2004/05/29 - 01:00

Done, and is working.

tbonfort commented 12 years ago

Author: sgillies@frii.com Date: 2004/09/22 - 17:22

Dropping this option from mapscript.  Will not be an option in 4.4.

MapServer / MapServer-import

Optional new names for Mapscript classes #587