Closed aske closed 5 years ago
Thanks for bringing this to our attention.
I'm not sure if it's the right approach as it would break compilation with smlnj versions before 110.94
We don't have a backwards compatibility policy and favor the latest version available once something breaks. I've pushed this patch to trunk and updated our test machine and configure scripts to use 110.95 or newer.
smlnj 110.95 (probably 110.94 too, as it switched the type of source-file positions from
Position.int
toInt.int
) can't build the latest revision of manticore:It works with the following change:
I'm not sure if it's the right approach as it would break compilation with smlnj versions before 110.94 (and I didn't see any pragmas/etc for backwards-compatibility of this sort; though I'm really new to SML and might've missed it). What's your usual approach to this?