Opened 20 years ago

Closed 20 years ago

Last modified 20 years ago

#587 closed defect (fixed)

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 (5)

comment:1 by sgillies@…, 20 years ago

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

comment:2 by sgillies@…, 20 years ago

This feature is now controlled by the NEXT_GENERATION_NAMES symbol.

comment:3 by sgillies@…, 20 years ago

Owner: changed from sdlime to sgillies@…
Status: assignednew

comment:4 by sgillies@…, 20 years ago

Resolution: fixed
Status: newclosed
Done, and is working.

comment:5 by sgillies@…, 20 years ago

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