More constants to be exposed to mapscript

[szekerest]

I would be useful to reconsider which of the constants used by mapserver 
should be exposed to mapscript.

For example MS_MAXLAYERS, MS_MAXSTYLES, MS_MAXCLASSES should be exposed 
because the layers, styles and classes can be added dynamically.

Tamas Szekeres

[sgillies@…]

Tamas, instances of layerObj can be added to a mapObj's layer array, yes, but
the *length* of the layer array cannot be changed except at compile time. The
actual number of layers in a map is found with map.numlayers.

I don't think it is unreasonable that we should have read access to these three
constants, but they can not be mutated in the current state of MapServer.

[szekerest]

Sean,

These constants should be exposed so as to make sure the number of elements 
(layers, classes, styles) will be less than the maximum before adding to the 
collection. However it cannot be guessed theese upper limits without adding 
them to the mapscript interface.  Certainly, theese constants shouldn't be 
modifyed at run time.

In addition I think that there is no reasonable sense to hide most of the 
constants, because the funcioning of the interface cannot be interfered by 
exposing them, but the absence may be cumbersome.

Tamas Szekeres
 

[sgillies@…]

OK, MS_MAXLAYERS, MS_MAXCLASSES, and MS_MAXSTYLES are exposed in the CVS HEAD
and for 4.8 beta2.