calling INT with float bounds results in a crash

[mzuenni]

According to the spec this should be a valid program (even though kind of weird):

INT(-0.5, 0.5) NEWLINE

But I get:

terminate called after throwing an instance of 'boost::wrapexcept<boost::bad_get>'
  what():  boost::bad_get: failed value get using boost::get

[mzuenni]

Using a float, or a string as an array index also seems to crash:

SET(a[1.0]=1)

SET(a[""]=1)

[eldering]

Indeed. The intention was that indices may be expressions, but must have integer type, but that's not made explicit in the specification. I think we should just make that explicit and also check and report better errors in your examples above.

[mzuenni]

For the indices I agree, but what is intended for INT?

INT(-0.5, 0.5) NEWLINE

Allowing or disallowing this would both be fine for me. (Currently checktestdata crashes => so its not allowed)

[eldering]

For the indices I agree, but what is intended for INT?

INT(-0.5, 0.5) NEWLINE

Allowing or disallowing this would both be fine for me. (Currently checktestdata crashes => so its not allowed)

I think the implicit assumption was that min and max have integer type, so we should make that explicit and also make the error message more explicit.