Adding version encoding for 0.14 spec.#512
Conversation
|
The goal was to make .14 backwards/forwards compatible with 0.13. There have been a few changes where that isn't the case, but they deal with corner cases that I don't expect anybody to notice. This would be an intentionally incompatible change. I'm not really against it, since all that would have to be changed is debuggers to recognize the new number. But I think we should think about whether we want this. |
|
Yeah, I probably should have raised this as an issue for discussion first, but the goal of this is just to put it on the radar and make sure we consider it before finalizing 0.14. |
|
There are changes since 0.13 that are backwards incompatible. The specific case I have in mind is #507 . This isn't theoretical: following the old FdmSbcsSbautoincrement text to the letter is incompatible with some versions of commercial debugger software available today. The debugger software needs to be able to discover which behavior it is potentially dealing with. |
timsifive
left a comment
timsifive
left a comment
There was a problem hiding this comment.
Per discussion in today's call, let's merge this. However, this change has tabs in a file that otherwise only uses spaces. Can you fix that?
3 participants
I'm of the view that there are sufficient changes in 0.14 to warrant a distinct encoding for the version. This pull request simply adds that encoding to the spec.