[Pharo-dev] [Pharo 9.0] Build #539: Compiler-OCAbstractMethodScope-push-node-down

There is a new Pharo build available! The status of the build #539 was: FAILURE. The Pull Request #6942 was integrated: "Compiler-OCAbstractMethodScope-push-node-down" Pull request url: https://github.com/pharo-project/pharo/pull/6942 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #538: ReImplementedNotSentRule-tellmeMore

There is a new Pharo build available! The status of the build #538 was: FAILURE. The Pull Request #6936 was integrated: "ReImplementedNotSentRule-tellmeMore" Pull request url: https://github.com/pharo-project/pharo/pull/6936 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #537: Variables-isReferenced-cleanup

There is a new Pharo build available! The status of the build #537 was: FAILURE. The Pull Request #6935 was integrated: "Variables-isReferenced-cleanup" Pull request url: https://github.com/pharo-project/pharo/pull/6935 Issue Url: https://github.com/pharo-project/pharo/issues/Variables Build

[Pharo-dev] what is newFrom:

Hi I’m spotting real inconsistency in the specification and use of newFrom: In Pharo and Object we have newFrom: aSimilarObject "Create an object that has similar contents to aSimilarObject. If the classes have any instance variables with the same names, copy them across. If this

[Pharo-dev] [Pharo 9.0] Build #536: Make RBComment a subclass of RBProgramNode

There is a new Pharo build available! The status of the build #536 was: SUCCESS. The Pull Request #6934 was integrated: "Make RBComment a subclass of RBProgramNode" Pull request url: https://github.com/pharo-project/pharo/pull/6934 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #535: Variables-isBlockVar-via-Variable

There is a new Pharo build available! The status of the build #535 was: FAILURE. The Pull Request #6926 was integrated: "Variables-isBlockVar-via-Variable" Pull request url: https://github.com/pharo-project/pharo/pull/6926 Issue Url: https://github.com/pharo-project/pharo/issues/Variables

[Pharo-dev] [Pharo 9.0] Build #534: 6928-BaselineOf-should-have-an-empty-baseline-class-method

There is a new Pharo build available! The status of the build #534 was: SUCCESS. The Pull Request #6932 was integrated: "6928-BaselineOf-should-have-an-empty-baseline-class-method" Pull request url: https://github.com/pharo-project/pharo/pull/6932 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #533: Variable-isSelf-isSuper-deprecation

There is a new Pharo build available! The status of the build #533 was: SUCCESS. The Pull Request #6930 was integrated: "Variable-isSelf-isSuper-deprecation" Pull request url: https://github.com/pharo-project/pharo/pull/6930 Issue Url: https://github.com/pharo-project/pharo/issues/Variable

[Pharo-dev] [Pharo 9.0] Build #532: Improving debugger infrastructure step 1: a Trait to unify the debugger API used by the system to open debuggers

There is a new Pharo build available! The status of the build #532 was: SUCCESS. The Pull Request #6901 was integrated: "Improving debugger infrastructure step 1: a Trait to unify the debugger API used by the system to open debuggers" Pull request url:

[Pharo-dev] [Pharo 9.0] Build #531: simplify-hasReportableSlip

There is a new Pharo build available! The status of the build #531 was: FAILURE. The Pull Request #6924 was integrated: "simplify-hasReportableSlip" Pull request url: https://github.com/pharo-project/pharo/pull/6924 Issue Url: https://github.com/pharo-project/pharo/issues/simplify Build Url: