Personally I am very firmly after backward compatibility (therefore adding to 2.0.0 milestone), but just noticed quite a list of open issues caused by legacy programming interfaces (get, mget, eval). I doubt below list is complete.
I would be open to deprecating these sooner than 2.0.0, but we definitely need to let the new programming interface mature for some time (e.g. 2-4 releases) before going that route.
Personally I am very firmly after backward compatibility (therefore adding to 2.0.0 milestone), but just noticed quite a list of open issues caused by legacy programming interfaces (get, mget, eval). I doubt below list is complete.
Bugs in special handling of scoping for variables
Special handling of scoping variable bugs during real/standard use of
eval()
Possibly bug introduced by special handling of
eval()