asFraction is missing in PartsPerFraction
There are currently no tests for any of the conversion methods.

• nthRoot:
• printOn:base:
• round:
• sqrt
• storeOn:base:

These messages may have been added to Pharo at some point in the superclass and now they are making PartsPerFraction lack the complete protocol.

So that one can use:

(1 2 3 4 5 6 7 8 9) chain select: [ :num | num even ];
                                       collect: [ :a | a / 2].

instead of:

((#(1 2 3 4 5 6 7 8 9) select: [ :num | num even ])
collect: [ :a | a / 2]).

If interesting, I have an implementation that uses Avatar that I can provide. The downside is that they don't have a proper baseline, so I had to fork the project in order to add one, issued a pull request, but up until today they did not integrated it: guillep/avatar#14

These tests in ExceptionHandlingSystemTest return an unexpected value in VA Smalltalk:

• testCatchingSetsOfExceptions
• testCatchingSetsOfExceptionsWithHierarchy
• testExceptionSetsConcatenation

This is because the implementation of \ is different when resuming a ZeroDivide error.

It's better to change occurrences of 1/0 to ZeroDivide signal.

When using the default option in the Icerberg UI to install a project with Metacello it will load the default group. When no default is declared apparently it loads all the packages that now include packages intended for use in GemStone 64 only.
Even if the docs are pointing the users to load one of the declared groups it will be less confusing for people loading the default one by mistake if the GS64 packages aren't included.

Hello,

[Pharo 12]

While trying to install Stargate on Pharo 12, I noticed I was loosing my text cursor.
After a long debug I finally got it down to Buoy, and more precisely something inside baselineGS64Development.
I also needed to disable baselineChronology (which I'm less happy about, as it feels it's probably useful for Pharo too..).
I don't know whether I'll continue to debug this.

To reproduce, just try to install Stargate and/or Buoy on its own.
(Buoy on its own crashes when installing the baseline, and loading GS64-extensions).

To test whether the bug is present:
Open a workspace/playground (the text cursor should be displayed in the initial state)

Shouldn't the packages GS64 be only loaded in a GS environment?

Pierre

Implement something to allow given an Optional get a new Optional instance applying a transformation block in case is used.

Background

Internationalization, often shortened to "i18n", is the practice of designing a system in such a way that it can easily be adapted for different target audiences, that may vary in region, language, or culture.
The complementary process of adapting a system for a specific target audience is called Localization. Localization (l10n) is the process of adapting a software user interface to a specific culture.

The following are common factors to consider:

• language
• unit of measure (e.g., kilometers in Europe, miles in U.S.)
• text direction (e.g., European languages are left-to-right, Arabic right-to-left)
• capitalization in Latin script (e.g., English uses capitals for weekdays, Spanish uses lowercase)
• adaptation of idioms (e.g., "raining cats and dogs" makes no sense when translated literally)
• use of register (e.g., in Japanese respectful speech differs exceptionally from casual speech)
• number format (e.g., 10 000,00 in Germany vs. 10,000.00 in the U.S.)
• date format
• currency
• cultural references
• paper size
• color psychology
• compliance with local laws
• local holidays
• personal names

Scope

This feature intends to provide basic building blocks easing the localization of an application using Buoy as a dependency. The initial scope includes:

• Basic support for translations (#126)
• Locale-aware number formatting
• Locale-aware chronology objects formatting (dates, times, etc)
• Extraction of translation units from source code
• Loading translations on an image

Other projects can complement this behavior once the building blocks are in place, like Aconcagua adding localization support for units of measure, Chalten adding localization support for its chronology abstractions, and so on.

Buoy-metaprogramming-extensions should be using group: 'Deployment' on the baseline of buoy at baselineMetaprogramming: but instead is missing. Check here

This may lead to MessageNotUnderstood Exceptions in many places like
#PropertyBasedEqualityChecker>>check: aBaseObject against: aTargetObject

Add StandardComparison and ExclusiveLogicalOr to compare objects