Squeak-dev December 2023

squeak-dev@lists.squeakfoundation.org

26 participants
124 discussions

The Inbox: Morphic-ct.2152.mcz
by commits＠source.squeak.org 19 Jan '24

19 Jan '24

Christoph Thiede uploaded a new version of Morphic to project The Inbox: http://source.squeak.org/inbox/Morphic-ct.2152.mcz ==================== Summary ==================== Name: Morphic-ct.2152 Author: ct Time: 26 December 2023, 6:55:20.675309 pm UUID: 6ac2adc4-972f-5746-b337-3e0c6279fc48 Ancestors: Morphic-ct.2150 Proposal: In docking bar window menus, displays specific expand/collapse/contract operation based on current window status. Possible disadvantages: Labels might be harder to find without icon, labels might be out of date in the rare scenario that windows open or change themselves while a windows menu is opened. =============== Diff against Morphic-ct.2150 =============== Item was added: + ----- Method: SystemWindow>>isExpanded (in category 'resize/collapse') ----- + isExpanded + ^ self unexpandedFrame notNil! Item was changed: ----- Method: TheWorldMainDockingBar>>windowMenuFor:on: (in category 'submenu - windows') ----- windowMenuFor: window on: menu | closeBox closeBoxWidth | closeBox := SystemWindow closeBoxImage. closeBoxWidth := closeBox width. menu addItem: [ :item | item contents: 'Close' translated ; icon: closeBox; target: window; selector: #closeBoxHit ]; + addItem: [ :item | - addItem: [ :item | item + contents: (window isExpanded ifFalse: ['Expand' translated] ifTrue: ['Contract' translated]) ; - contents: 'Expand (or contract)' translated ; icon: (MenuIcons blankIconOfWidth: closeBoxWidth); target: window; selector: #expandBoxHit ]; addItem: [ :item | item + contents: (window isCollapsed ifFalse: ['Collapse' translated] ifTrue: ['Expand' translated]) ; - contents: 'Collapse (or expand)' translated ; icon: (MenuIcons blankIconOfWidth: closeBoxWidth); target: window; selector: #collapseOrExpand ]; addLine; addItem: [ :item | item contents: 'Close all like this' translated ; icon: closeBox; target: self; selector: #closeAllWindowsLike:; arguments: { window } ]; addItem: [ :item | item contents: 'Close all but this' translated ; icon: (MenuIcons blankIconOfWidth: closeBoxWidth); target: self; selector: #closeAllWindowsBut:; arguments: { window } ]; addLine; addItem: [ :item | item contents: 'Collapse all like this' translated ; icon: (MenuIcons blankIconOfWidth: closeBoxWidth); target: self; selector: #collapseAllWindowsLike:; arguments: { window } ]; addItem: [ :item | item contents: 'Collapse all but this' translated ; icon: (MenuIcons blankIconOfWidth: closeBoxWidth); target: self; selector: #collapseAllWindowsBut:; arguments: { window } ]!

2 1

The Inbox: Collections-ct.1060.mcz
by commits＠source.squeak.org 19 Jan '24

19 Jan '24

Christoph Thiede uploaded a new version of Collections to project The Inbox: http://source.squeak.org/inbox/Collections-ct.1060.mcz ==================== Summary ==================== Name: Collections-ct.1060 Author: ct Time: 27 December 2023, 11:59:34.927399 pm UUID: 97958301-3160-e74c-9b2f-46c22493a381 Ancestors: Collections-mt.1058 Speeds up printing of large sets. Analogously to dictionaries, do not sort and enumerate all their items beyond a threshold. =============== Diff against Collections-mt.1058 =============== Item was changed: ----- Method: Set>>printElementsOn: (in category 'printing') ----- printElementsOn: aStream "Like dictionaries, indicate some human-readable sort order." + self size > 100 ifTrue: + [aStream + nextPutAll: '(size '; + print: self size; + nextPut: $). + ^ self]. + self sortedSafely printElementsOn: aStream.!

2 1

Re: [Newbies] Help with keyboard layout when typing a caret
by lewis＠mail.msen.com 15 Jan '24

15 Jan '24

On 2023-12-30 16:51, Ivan Reche wrote: > Hey there! > > Total newbie here. Hello Ivan, Happy holidays and welcome to Squeak! > I'm playing with Squeak on my vacation and I've noticed that, whenever > I try to type a caret (^), which I believe is core to using Smalltalk, > Squeak will insert an interrogation mark (?) in its place. I believe it > must be something related to keyboard layout, but I have no idea on how > to troubleshoot and fix this. > > Here is a screenshot to show what's happening: > > My keyboard layout works just fine on GNOME. Thanks in advance! > > My environment: > OS: Linux (GNOME DE) > Keyboard layout: Portuguese ABNT2 > Squeak version: Squeak6.0-22104-64bit-202206021410-Linux-x64 I do not know the answer to your question, but it may be a complex issue so I am CC'ing the squeak-dev developers' list for help. From what I can gather from a search on the net (https://kbdlayout.info/KBDBR/), the caret key may require some special handling for the Portuguese ABNT2 keyboard. Possibly gnome knows about this and Squeak does not. Does anyone on the squeak-dev list have a tip for how to enter a caret (^) on a Portuguese ABNT2 keyboard? Replies should include to the beginners list please. Screen shots from the original message (I cannot forward them) are at https://lists.squeakfoundation.org/archives/list/beginners@lists.squeakfoun… Dave

5 7

Code duplication around unwinding
by Jaromir Matas 14 Jan '24

14 Jan '24

Hi all, When I started learning Squeak I wondered why so much code duplication around unwinding: Context>>#restart, #resume:through:, #resumeEvaluating:, #terminate and #unwindTo: all implementing the exact same algorithm. Kernel-jar.1499 suggests removing all this duplicity while keeping the current unwind semantics. All Process and Exceptions tests are green. This changeset is the first step in my effort to reduce the "noise" around the "collection" of resume/return methods in Context and Exception. One idea is to return calling the unwind mechanism back to the Exception class, as originally implemented in Squeak 2.x up to 3.5; please let me know if you find something fundamentally wrong with this idea. Example: I find this call sequence begging for simplification: Exception>>resume: --> resumeUnchecked: --> resumeEvaluating: --> Context>>returnEvaluating: --> resumeEvaluating: Best, Jaromir -- Jaromír Matas mail(a)jaromir.net

2 9

[ANN] TraceDebugger: A new time-travel debugger for Squeak
by christoph.thiede＠student.hpi.uni-potsdam.de 13 Jan '24

13 Jan '24

Hi all! I‘m very excited to announce a project today that we have been working on over the past two years: The TraceDebugger [1] is a new back-in-time/time-travel/omniscient debugging tool for Squeak that allows you to record past method activations and states during execution and explore them later. https://github.com/hpi-swa-lab/squeak-tracedebugger Metacello new baseline: 'TraceDebugger'; repository: 'github://hpi-swa-lab/squeak-tracedebugger'; "repository: 'github://hpi-swa-lab/squeak-tracedebugger:squeak60';" "for Squeak 6.0" get; load. *What can it do? (Features)* - Record all method activations and historic states: Normally step through a program in the debugger while automatically recording its execution. - Replay execution of a traced program: Navigate through all method invocations using the *context tree* or the *Step Back/Step Forward* buttons (to avoid these "oops, I‘ve stepped too far, let‘s start all over again" situations). - Interact with historic states: Inspect/explore snapshots of objects or send them any message. - State-centric debugging using the *History Explorer*: Gather, explore, and visualize all changes to an object/expression over the recorded time ("When did this variable/collection/screenshot change?"). - Additional navigation tools for searching and filtering the context tree. - Focus on interactivity: No hours of recording, no GBs of mem consumption - at least for common small to medium programs. - UI resembles the classic Smalltalk debugger: You'll find your familiar stepping buttons, code browsing tools, inspectors, and shortcuts - plus more. The TraceDebugger is a general-purpose tool and not tied to particular domains. In the past months, we have successfully used it to understand several bugs and interaction patterns in the Trunk (Morphic layout/rendering, compiler/decompiler, code simulation, …). The tool is also self-supporting, so you can debug a TraceDebugger from another TraceDebugger. :-) *What can‘t it do (yet)? (Limitations and future work)* - High performance: While (sufficiently) fast enough for most small to medium workloads, tracing very compute- or mem-intensive operations may require more time (ex.: compiler/decompiler invocation: <1s, HTTPS request: <10s, tool building: <5m, complex rendering: minutes up to hours). - Not a dataflow analyzer: The TraceDebugger does not track dataflow events (e.g., argument passing) but only state changes. - No tracing of external states/events for FFI/OSProcess or custom VM modules. - No support for advanced language concepts such as identity forwarding/write barriers. *How does it work? (Implementation)* In one sentence: To record message sends and side effects, we decorate the execution of certain bytecodes with tracing extensions by modifying the code simulation using SimulationStudio [2]. In one paragraph: The program is executed in a specialized code simulator that overrides instructions for sending messages (e.g., send, superSend) and for performing side-effects (e.g., popIntoRcvr, primitiveAtPut, push). All message sends are recorded in a tree and all changed object slots are stored in a sparse time-dependent memory structure before they are overwritten. For time-traveling, the tree is traversed using a cursor. For accessing historic objects, a proxy evaluates all messages sent to an object in another specialized simulator (retracing simulator) that emulates historic states for the requested point in time by forwarding read primitives (e.g., pushRcvr, primitiveAt) to the recorded memory. For gathering state changes in the History Explorer efficiently, the query is evaluated in a range retracing simulator with vectorization and fork semantics. In academic terms: We have published two papers about the TraceDebugger that provide further details about its implementation and its applications for program exploration, "Object-Centric Time-Travel Debugging: Exploring Traces of Objects" [3] and "Time-Awareness in Object Exploration Tools: Toward In Situ Omniscient Debugging" [4]. In Smalltalk: Just check out the code base and explore it by yourself! The class comments in TraceDebugger and TDBCursor should provide good starting points. *How can I use it?* Please try it out and report feedback! The TraceDebugger supports the latest Squeak Trunk and Squeak 6.0. You can either download a prepared all-in-one bundle on GitHub: https://github.com/hpi-swa-lab/squeak-tracedebugger/releases Or you can install it into your own image using Metacello: Metacello new baseline: 'TraceDebugger'; repository: 'github://hpi-swa-lab/squeak-tracedebugger'; "repository: 'github://hpi-swa-lab/squeak-tracedebugger:squeak60';" "for Squeak 6.0" get; load. To get started, just open a normal debugger (e.g., by selecting an expression and pressing Cmd+Shift+D to debug it) and then press the "Trace It" button on the right. There‘s also some pretty detailed documentation in the Help Browser that covers everything you should know. My goal is to improve convenience and provide a useful tool for the community, so I‘m very excited to hear your impressions, ideas, and thoughts. Here, on GitHub, or in a private message. Let‘s have a great discussion! :-) Best, Christoph (and Marcel) PS: Props to Eliot who brought up the original idea of "subclassing from Context" for other reasons four years ago. [5] [1] https://github.com/hpi-swa-lab/squeak-tracedebugger [2] https://github.com/LinqLover/SimulationStudio [3] Christoph Thiede, Marcel Taeumel, and Robert Hirschfeld. 2023. Object-Centric Time-Travel Debugging: Exploring Traces of Objects. In Companion Proceedings of the 7th International Conference on the Art, Science, and Engineering of Programming (<Programming>'23 Companion), March 13–17, 2023, Tokyo, Japan. ACM, New York, NY, USA, 7 pages. DOI: 10.1145/3594671.3594678. PDF: https://dl.acm.org/doi/pdf/10.1145/3594671.3594678 [4] Christoph Thiede, Marcel Taeumel, and Robert Hirschfeld. 2023. Time-Awareness in Object Exploration Tools: Toward In Situ Omniscient Debugging. In Proceedings of the 2023 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software (Onward! '23), October 25–27, 2023, Cascais, Portugal. ACM, New York, NY, USA, 14 pages. DOI: 10.1145/3622758.3622892. PDF: https://dl.acm.org/doi/pdf/10.1145/3622758.3622892 [5] http://lists.squeakfoundation.org/pipermail/squeak-dev/2019-October/204803.… --- Sent from Squeak Inbox Talk

4 22

The Inbox: Kernel-ct.1448.mcz
by commits＠source.squeak.org 09 Jan '24

09 Jan '24

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-ct.1448.mcz ==================== Summary ==================== Name: Kernel-ct.1448 Author: ct Time: 12 March 2022, 12:42:08.516359 am UUID: 7659c202-5fcc-084e-84b4-a5d233717b2d Ancestors: Kernel-nice.1447 Implements missing simulation of primitive 189 primitiveExecuteMethod (Object>>with:...executeMethod:). =============== Diff against Kernel-nice.1447 =============== Item was changed: ----- Method: Context>>doPrimitive:method:receiver:args: (in category 'private') ----- doPrimitive: primitiveIndex method: meth receiver: receiver args: arguments "Simulate a primitive method whose index is primitiveIndex. The simulated receiver and arguments are given as arguments to this message. If successful, push result and return resuming context, else ^ {errCode, PrimitiveFailToken}. Any primitive which provokes execution needs to be intercepted and simulated to avoid execution running away." | value | "Judicious use of primitive 19 (a null primitive that doesn't do anything) prevents the debugger from entering various run-away activities such as spawning a new process, etc. Injudicious use results in the debugger not being able to debug interesting code, such as the debugger itself. Hence use primitive 19 with care :-)" "SystemNavigation new browseAllSelect: [:m| m primitive = 19]" primitiveIndex = 19 ifTrue: [ [self notify: ('The code being simulated is trying to control a process ({1}). Process controlling cannot be simulated. If you proceed, things may happen outside the observable area of the simulator.' translated format: {meth reference})] ifCurtailed: [self push: nil "Cheap fix of the context's internal state"]]. ((primitiveIndex between: 201 and: 222) and: [(self objectClass: receiver) includesBehavior: BlockClosure]) ifTrue: [(primitiveIndex = 206 or: [primitiveIndex = 208]) ifTrue: "[Full]BlockClosure>>valueWithArguments:" [^receiver simulateValueWithArguments: arguments first caller: self]. ((primitiveIndex between: 201 and: 209) "[Full]BlockClosure>>value[:value:...]" or: [primitiveIndex between: 221 and: 222]) ifTrue: "[Full]BlockClosure>>valueNoContextSwitch[:]" [^receiver simulateValueWithArguments: arguments caller: self]]. primitiveIndex = 83 ifTrue: "afr 9/11/1998 19:50" "Object>>perform:[with:...]" [| selector | selector := arguments at: 1 ifAbsent: [^ self class primitiveFailTokenFor: #'bad argument']. arguments size - 1 = selector numArgs ifFalse: [^ self class primitiveFailTokenFor: #'bad number of arguments']. ^self send: selector to: receiver with: arguments allButFirst]. primitiveIndex = 84 ifTrue: "afr 9/11/1998 19:50 & eem 8/18/2009 17:04" "Object>>perform:withArguments:" [| selector args | arguments size = 2 ifFalse: [^ self class primitiveFailTokenFor: #'bad argument']. selector := arguments first. args := arguments second. args isArray ifFalse: [^ self class primitiveFailTokenFor: #'bad argument']. args size = selector numArgs ifFalse: [^ self class primitiveFailTokenFor: #'bad number of arguments']. ^self send: selector to: receiver with: args]. primitiveIndex = 100 ifTrue: "eem 8/18/2009 16:57" "Object>>perform:withArguments:inSuperclass:" [| rcvr selector args superclass | arguments size caseOf: { [3] -> [ rcvr := receiver. selector := arguments first. args := arguments second. superclass := arguments third]. [4] -> ["mirror primitive" rcvr := arguments first. selector := arguments second. args := arguments third. superclass := arguments fourth] } otherwise: [^ self class primitiveFailTokenFor: #'bad argument']. args isArray ifFalse: [^ self class primitiveFailTokenFor: #'bad argument']. args size = selector numArgs ifFalse: [^ self class primitiveFailTokenFor: #'bad number of arguments']. ((self objectClass: rcvr) includesBehavior: superclass) ifFalse: [^ self class primitiveFailTokenFor: #'bad argument']. ^self send: selector to: rcvr with: args lookupIn: superclass]. "Mutex>>primitiveEnterCriticalSection Mutex>>primitiveTestAndSetOwnershipOfCriticalSection" (primitiveIndex = 186 or: [primitiveIndex = 187]) ifTrue: [| effective | effective := Processor activeProcess effectiveProcess. "active == effective" value := primitiveIndex = 186 ifTrue: [receiver primitiveEnterCriticalSectionOnBehalfOf: effective] ifFalse: [receiver primitiveTestAndSetOwnershipOfCriticalSectionOnBehalfOf: effective]. ^(self isPrimFailToken: value) ifTrue: [value] ifFalse: [self push: value]]. + + (primitiveIndex = 188 or: [primitiveIndex = 189]) ifTrue: - - primitiveIndex = 188 ifTrue: "Object>>withArgs:executeMethod: - CompiledMethod class>>receiver:withArguments:executeMethod: - VMMirror>>ifFail:object:with:executeMethod: et al" [| n args methodArg thisReceiver | + primitiveIndex caseOf: + {[188 "primitiveExecuteMethodArgsArray"] -> + ["Object>>withArgs:executeMethod: + CompiledMethod class>>receiver:withArguments:executeMethod: + VMMirror>>ifFail:object:with:executeMethod: et al" + ((n := arguments size) between: 2 and: 4) ifFalse: + [^self class primitiveFailTokenFor: #'unsupported operation']. + ((self objectClass: (args := arguments at: n - 1)) == Array + and: [(self objectClass: (methodArg := arguments at: n)) includesBehavior: CompiledMethod]) ifFalse: + [^self class primitiveFailTokenFor: #'bad argument']. + thisReceiver := arguments at: n - 2 ifAbsent: [receiver]]. + [189 "primitiveExecuteMethod"] -> + ["Object>>executeMethod: + Object>>with:...executeMethod:" + (arguments size > 0) ifFalse: + [^self class primitiveFailTokenFor: #'bad argument']. + ((self objectClass: (methodArg := arguments atLast: 1)) includesBehavior: CompiledMethod) ifFalse: + [^self class primitiveFailTokenFor: #'bad argument']. + args := arguments allButLast. + thisReceiver := receiver]}. - ((n := arguments size) between: 2 and: 4) ifFalse: - [^self class primitiveFailTokenFor: #'unsupported operation']. - ((self objectClass: (args := arguments at: n - 1)) == Array - and: [(self objectClass: (methodArg := arguments at: n)) includesBehavior: CompiledMethod]) ifFalse: - [^self class primitiveFailTokenFor: #'bad argument']. methodArg numArgs = args size ifFalse: [^self class primitiveFailTokenFor: #'bad number of arguments']. - thisReceiver := arguments at: n - 2 ifAbsent: [receiver]. methodArg primitive > 0 ifTrue: [methodArg isQuick ifTrue: [^self push: (methodArg valueWithReceiver: thisReceiver arguments: args)]. ^self doPrimitive: methodArg primitive method: meth receiver: thisReceiver args: args]. ^self activateMethod: methodArg withArgs: args receiver: thisReceiver]. primitiveIndex = 118 ifTrue: "[receiver:]tryPrimitive:withArgs:; avoid recursing in the VM" [(arguments size = 3 and: [(self objectClass: arguments second) == SmallInteger and: [(self objectClass: arguments last) == Array]]) ifTrue: [^self doPrimitive: arguments second method: meth receiver: arguments first args: arguments last]. (arguments size = 2 and: [(self objectClass: arguments first) == SmallInteger and: [(self objectClass: arguments last) == Array]]) ifFalse: [^self class primitiveFailTokenFor: nil]. ^self doPrimitive: arguments first method: meth receiver: receiver args: arguments last]. value := primitiveIndex = 120 "FFI method" ifTrue: [(meth literalAt: 1) tryInvokeWithArguments: arguments] ifFalse: [primitiveIndex = 117 "named primitives" ifTrue: [self tryNamedPrimitiveIn: meth for: receiver withArgs: arguments] ifFalse: "should use self receiver: receiver tryPrimitive: primitiveIndex withArgs: arguments but this is only in later VMs (and appears to be broken)" [receiver tryPrimitive: primitiveIndex withArgs: arguments]]. ^(self isPrimFailToken: value) ifTrue: [value] ifFalse: [self push: value]!

4 5

Let's discuss the future of Etoys in Squeak 6.1 (and beyond)
by Marcel Taeumel 02 Jan '24

02 Jan '24

Hi all -- Please find attached a change-set that unloads Etoys from Squeak 6.1alpha #22748 (and later). Let us use this artifact to discuss the future of Etoys in Squeak 6.1 and beyond. You can use Monticello or the ChangeSorter to take a look at what's needed besides unloading the Etoys package itself. Also check preamble and postscript of the attached change-set. !!! Yes, simply re-loading the Etoys package is not enough to restore basic Etoys functionality. There are several sub-method changes needed for the Etoys integration into the base system. Here is what would still work through the package MorphicExtras: - Games - Sketches and PaintBox - Flaps - CalendarMorph - SpectrumAnalyzerMorph Here is what would still "work" through the package System: - Object storage (ImageSegment etc.) - ProjectLoading Here is what would still work through the package Protocols: - Lexicon tool - Vocabulary framework Here is what would be gone: - Tiles, viewers, and scripts - Players and costumes - Pen trails, Turtles, ... - References, CustomEventsRegistry, ScriptingSystem - Siblings for (Player-only) uni-classes - DeepCopier support for (Player-only) uni-classes - Preferences #noviceMode, #eToyFriendly, and more Note that we still have several Etoys-compatible releases such as Etoys 4/5/6 and Squeak 5.1/5.2/5.3/6.0. Best compatibility is probably with Etoys 5. Most updated base system is probably Squeak 6.0. :-) So...should we remove Etoys from Trunk at this point? Please share your thoughts. And feel free to also report issues with loading/using the attached change-set itself. Best, Marcel

14 30

The Trunk: KernelTests-jar.448.mcz
by commits＠source.squeak.org 30 Dec '23

30 Dec '23

Christoph Thiede uploaded a new version of KernelTests to project The Trunk: http://source.squeak.org/trunk/KernelTests-jar.448.mcz ==================== Summary ==================== Name: KernelTests-jar.448 Author: jar Time: 30 December 2023, 6:28:02.589852 pm UUID: 058e235e-90d4-d648-9442-b468fee2bb2e Ancestors: KernelTests-jar.447 Test if #return:from: correctly handles returns to dead or nil contexts. =============== Diff against KernelTests-jar.447 =============== Item was added: + ----- Method: ContextTest>>testBlockCannotReturn (in category 'tests') ----- + testBlockCannotReturn + "Test if #return:from: correctly handles returns to dead or nil contexts." + + | p | + p := [ thisContext pc: nil ] newProcess. + p runUntil: [:ctx | ctx method selector = #pc: and: [ctx sender isDead]]. + + "assert p stoped at the last instruction, i.e. a return, of #pc: + and is about to return to a dead context" + self assert: p suspendedContext method selector equals: #pc:. + self assert: p suspendedContext sender isDead. + self assert: p suspendedContext willReturn. + self assert: p suspendedContext atEnd. + + p step. "step into a return to a dead sender" + + self assert: p suspendedContext method selector = #cannotReturn:!

1 0

[Simulation errors] ObjectTracer on: true
by Thiede, Christoph 30 Dec '23

30 Dec '23

Hi all! I rarely discovered that much errors with one single command :-) Steps to reproduce Print it: (ObjectTracer on: true) ifTrue: [1] Expected behavior It is printed: 1 Actual behavior The following tracer notifications appear (proceed them all): 1. (3x) #printStringLimitedTo:, #longPrintOn:limitedTo:indent: and again #printStringLimitedTo:, caused by SmalltalkImage >> #logSqueakError:inContext: 2. #mustBeBoolean 3. (3 more print message called by #logSqueakError:inContext: again, see the next error) 4. Error: Where's the jump? Caused by #mustBeBooleanIn:, #skipBackBeforeJump If you still keep proceeding: 1. (3 more print message called by #logSqueakError:inContext: again, see the next error) 2. Finally, the NonBooleanReceiver error from 2. 3. VM crashes. Summarizing the bugs ObjectTracer traces too much The amount of messages printed by the ObjectTracer is an unintended side effect of the way it signals calls via the debugger. The debugger logs this error, including the stack trace. How can we avoid this? Should we suppress all further notifications from one ObjectTracer instance during the first one is debugged? #mustBeBoolean is sent to boolean proxy This is caused by the simulation of the inlined #ifTrue: call. I don't know whether this is worth to be fixed before Scorch? If yes, I think we would need to disable inlining for this particular selector or make inlining opt-out-able as proposed here (this would probably be way too slow)<http://forum.world.st/The-Inbox-HelpSystem-Core-ct-123-mcz-tp5105402p511363…>. #mustBoBoolean depends on caller chain It turns out that #mustBeBoolean relies on being called from a context that just did a jump. This makes it impossible to forward this message as usual via a transparent proxy/decorator. We use this pattern in other methods as well. How can we enable transparent wrappers not to collide with method contexts depending on their sender? Best, Christoph

6 11

The Inbox: Kernel-ct.1548.mcz
by commits＠source.squeak.org 30 Dec '23

30 Dec '23

Christoph Thiede uploaded a new version of Kernel to project The Inbox: http://source.squeak.org/inbox/Kernel-ct.1548.mcz ==================== Summary ==================== Name: Kernel-ct.1548 Author: ct Time: 30 December 2023, 8:57:59.873665 pm UUID: 0b32cb51-9e96-d247-be53-734ad1f2735f Ancestors: Kernel-ct.1545 Proposal: Resolves #mustBeBoolean errors for copies or proxies for true and false. For instance, the following now works: True basicNew ifTrue: [1] ifFalse: [2]. (ObjectTracer on: false) ifTrue: [1] ifFalse: [2]. See: https://lists.squeakfoundation.org/archives/list/squeak-dev@lists.squeakfou… =============== Diff against Kernel-ct.1545 =============== Item was added: + ----- Method: False>>mustBeBooleanIn: (in category 'as yet unclassified') ----- + mustBeBooleanIn: aContext + + aContext skipBackBeforeJump. + ^ false! Item was added: + ----- Method: ObjectTracer>>mustBeBoolean (in category 'very few messages') ----- + mustBeBoolean + "Overwritten to preserve original sender context." + + ^ self mustBeBooleanIn: thisContext sender! Item was added: + ----- Method: True>>mustBeBooleanIn: (in category 'as yet unclassified') ----- + mustBeBooleanIn: aContext + + aContext skipBackBeforeJump. + ^ true!

1 0