abnormal program termination when having multiple PROJECTION

[bartvde@…]

When your PROJECTION is defined twice in the MAP file, you get an abnormal
program termination. This is the excerpt from the Apache error log:

Premature end of script headers: mapserv.exe
Assertion failed: p->proj == NULL, file mapfile.c, line 790
abnormal program termination

[sdlime]

So what's the proper behavior, assume the second projection or fail a bit more
gracefully?

[dmorissette]

I would say that we should give a fatal error (and fail gracefully) since having
2 projections is illegal.

[dmorissette]

Sounds like an easy one to fix for 4.2.  Do we all agree on producing a fatal
error if more than one projection is defined?

[sdlime]

Yup, cause this will only occur when the developer is setting up and debugging
an app.

[dmorissette]

Fixed.  I left the assert() in msProcessProjection(), but I added a msSetError()
inside loadProjection() so that the message shows up only if it happens during
mapfile parsing (it also includes the line number).

The assert() should never show up again unless some code somewhere does
something wrong which is what asserts are for.