Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
Not a huge fan of this but I can understand the compatibility concern. I think we do need a plan to eventually match scintilla (i.e. have a consistent API too).
E.g.
sci_get_selected_text_length2() with the new behavior and deprecate sci_get_selected_text_length() nowsci_get_selected_text_length() at some later pointsci_get_selected_text_length() at some even more later pointWe could also introduce some mechanism where plugins declare a API TARGET. E.g. if they target 242 (or none, because it's new) they get the old behavior, if they target 243 they get the new behavior.
Obviously this works only for cases where we can handle the behavior change at compile time and in header-only.
At some point we could reject plugins that target too old APIs (always with good reason, not "just because").
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.