[Mapserver-dev] Next Generation MapScript API

[Frank Warmerdam]

Paul Spencer wrote:
> is this intended to affect the swig-generated mapscript API and the 
> php_mapscript API?  There is a significant push to release 4.2 in the 
> very near future and if this change is made, it is unlikely that 
> php_mapscript could be rewritten to conform to the new API.
> 
> I would rather see the MapScript API NG reserved for the next mapserver 
> release (4.4) which would give everyone more time to both implement and 
> test for compatibility.  I must admit that I have a large toolkit built 
> on php_mapscript that I am trying to release right now and it requires 
> 4.1/4.2 for many features, so I will have a very significant delay in 
> releasing it if this change is implemented for 4.2 :(

Paul,

I have hadn't been thinking of changing the PHP side, though in the longer term
we do need to think about how to keep the PHP reasonably in sync with the
SWIG based MapScript implementations.

I would be amendable to deferring "next generation" SWIG MapScript roll out
to post-4.2 release.    Currently (as I understand it) the default is to not
use the next generation api stuff.

Best regards,

-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent