[pharo-project/pharo-core] 7c2c6d: 30857
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 7c2c6dfbde65dc30899e73fef6b39e91da860471 https://github.com/pharo-project/pharo-core/commit/7c2c6dfbde65dc30899e73fef... Author: Jenkins Build Server <board@pharo-project.org> Date: 2014-09-18 (Thu, 18 Sep 2014) Changed paths: A Collections-Strings.package/String.class/instance/converting/uncapitalized.st A Collections-Strings.package/Symbol.class/instance/converting/uncapitalized.st A CollectionsTests.package/StringTest.class/instance/tests - converting/testUncapitalized.st A CollectionsTests.package/SymbolTest.class/instance/tests/testUncapitalized.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script119.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30857.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-PolyWidgets.package/DateModel.class/instance/initialization/initializeWidgets.st Log Message: ----------- 30857 14018 backport #uncapitalized to Pharo3 https://pharo.fogbugz.com/f/cases/14018 14025 DateModel Broken in 3.0 https://pharo.fogbugz.com/f/cases/14025 http://files.pharo.org/image/30/30857.zip
GitHub wrote
14018 backport #uncapitalized to Pharo3
Not a big deal, but this doesn't seem to fit our bugfix-only backport policy. What was the rationale? ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-7c2c6d-30857-tp4778741p477874... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 18 Sep 2014, at 14:30, Sean P. DeNigris <sean@clipperadams.com> wrote:
GitHub wrote
14018 backport #uncapitalized to Pharo3
Not a big deal, but this doesn't seem to fit our bugfix-only backport policy. What was the rationale?
To allow external framework writers to target both 3 and 4 when renames/deprecations occur. Without moving the new method to 3, there is a catch 22: - either use the old API -> deprecation warning on 4 - either use the new API -> not available on 3 This will of course not be done for every change ;-) Marcus explained this in more detail in a mail.
On 18 Sep 2014, at 14:30, Sean P. DeNigris <sean@clipperadams.com> wrote:
GitHub wrote
14018 backport #uncapitalized to Pharo3
Not a big deal, but this doesn't seem to fit our bugfix-only backport policy. What was the rationale?
The rational is: Simplify API evolution. If we deprecate a method in Pharo4, people like to change their code base *and* use the same code on Pharo3. (Zinc is one example of that). So for simple ârenameâ changes like this, we can reduce the pain of people *a lot* by providing the same method in Pharo3. Keep in mind that we do *not* do the actual change of rewriting all senders and deprecating the old method. That is just done in Pharo4. Marcus
On Sep 18, 2014, at 8:35 AM, Marcus Denker-4 [via Smalltalk] <ml-node+s1294792n4778745h83@n4.nabble.com> wrote:
The rational is: Simplify API evolution. ⦠we can reduce the pain of people *a lot*
Ah, oh cool. Thanks for the explanation :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/pharo-project-pharo-core-7c2c6d-30857-tp4778741p477874... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (5)
-
Ben Coman -
GitHub -
Marcus Denker -
Sean P. DeNigris -
Sven Van Caekenberghe