Ticket #587 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

Optional new names for Mapscript classes

Reported by: sgillies@… Owned by: sgillies@…
Priority: high Milestone:
Component: MapScript Version: 4.1
Severity: normal Keywords:
Cc:

Description

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.

Change History

Changed 9 years ago by sgillies@…

  • status changed from new to assigned
Have added directives in mapscript.i that do the renaming.  New test cases
for the next generation classes pass.

Changed 9 years ago by sgillies@…

This feature is now controlled by the NEXT_GENERATION_NAMES symbol.

Changed 9 years ago by sgillies@…

  • owner changed from sdlime to sgillies@…
  • status changed from assigned to new

Changed 9 years ago by sgillies@…

  • status changed from new to closed
  • resolution set to fixed
Done, and is working.

Changed 9 years ago by sgillies@…

Dropping this option from mapscript.  Will not be an option in 4.4.
Note: See TracTickets for help on using tickets.