[Mapserver]36 to 40 converstion OVERLAY Objects are LOST!

[thorne@…]

I have confirmed that when converting a simple 36 map file to 40 with OVERLAY 
Objects in the class, the OVRLAY Definition is not put into a second Style 
object for that class. It is lost, during the conversion.

eg.

INPUT for Converstion ->Mapserver 36 Class Definision:
    CLASS
      NAME "Interstates"
      EXPRESSION "Interstate"
      SYMBOL "circle"
      COLOR 51 51 51
      SIZE 4
      OVERLAYSYMBOL "circle"
      OVERLAYCOLOR 220 0 0
      OVERLAYSIZE 2
    END
OUTPUT from the Conversion -> Mapserver 40:

    CLASS
      NAME "Interstates"
      EXPRESSION "Interstate"
      STYLE
        SYMBOL "circle"
        COLOR 51 51 51
        SIZE 4
        MINSIZE 1
        MAXSIZE 100
      END
    END

WHAT IT SHOULD BE:

    CLASS
      NAME "Interstates"
      EXPRESSION "Interstate"
      #-----------------
      #THE OVERLAY STYLE
      #-----------------
      STYLE
        SYMBOL "circle"
        COLOR 51 51 51
        SIZE 4
        MINSIZE 1
        MAXSIZE 100
      END
      #-----------------
      #THE BOTTOM STYLE
      #-----------------      
      STYLE
        SYMBOL "circle"
        COLOR 51 51 51
        SIZE 4
        MINSIZE 1
        MAXSIZE 100
      END
    END

Note: Notice that the Overlay Style is positions on top of the original symbol 
style. I am not sure if this is an issue when building your class where you 
have to place the styles in a specific order. If it is we should have a 
STYLEORDER Object, maybe (?)....

[dmorissette]

Assigning to myself, I'll look into this now.

[dmorissette]

Here is what I get as output after loading and saving your class definition
using the latest PHP MapScript 4.0 from CVS:

    CLASS
      NAME "Interstates"
      EXPRESSION "Interstate"
      STYLE
          COLOR 51 51 51
        MAXSIZE 100
        MINSIZE 1
        SIZE 4
        SYMBOL "circle"
      END
      STYLE
          COLOR 220 0 0
        MAXSIZE 100
        MINSIZE 1
        SIZE 2
        SYMBOL "circle"
      END
    END

So this is not a MapServer bug.  I believe you were getting this out of MapEdit?
 You should probably file this as a MapEdit bug then.  I'll mark this one as
INVALID.

For reference I'll attach to this bug the mapfile and script that I used for
testing.

[dmorissette]

ZIP file with the PHP script and mapfile used for testing this