Squeak-dev December 2023

squeak-dev@lists.squeakfoundation.org

26 participants
124 discussions

The Inbox: Nebraska-ct.63.mcz
by commits＠source.squeak.org 26 Dec '23

26 Dec '23

Christoph Thiede uploaded a new version of Nebraska to project The Inbox: http://source.squeak.org/inbox/Nebraska-ct.63.mcz ==================== Summary ==================== Name: Nebraska-ct.63 Author: ct Time: 26 December 2023, 6:21:39.784645 pm UUID: d062e798-696e-1b4b-a12c-4ab30556e670 Ancestors: Nebraska-dtl.61 Gently handles refused peer-to-peer connections, such as when sending an object from the client to the host. =============== Diff against Nebraska-dtl.61 =============== Item was changed: ----- Method: NebraskaPeerToPeer>>doConnectForSend (in category 'sending') ----- doConnectForSend | addr port | addr := NetNameResolver addressForName: (ipAddress copyUpTo: $:). addr ifNil: [ communicatorMorph commResult: {#message -> ('could not find ',ipAddress)}. ^false]. port := (ipAddress copyAfter: $:) asInteger. port ifNil: [port := self class eToyCommunicationsPorts first]. socket connectNonBlockingTo: addr port: port. [socket waitForConnectionFor: 15] + on: ConnectionRefused , ConnectionTimedOut - on: ConnectionTimedOut do: [:ex | communicatorMorph commResult: {#message -> ('no connection to ',ipAddress,' (', ipAddress,')')}. ^false]. ^true !

1 0

The Inbox: Nebraska-ct.62.mcz
by commits＠source.squeak.org 26 Dec '23

26 Dec '23

Christoph Thiede uploaded a new version of Nebraska to project The Inbox: http://source.squeak.org/inbox/Nebraska-ct.62.mcz ==================== Summary ==================== Name: Nebraska-ct.62 Author: ct Time: 26 December 2023, 6:20:04.348645 pm UUID: 4a2695e0-fdc7-194d-abc4-6c565e2deabe Ancestors: Nebraska-dtl.61 Fixes event position offsets for Nebraska terminals. Now one can move, resize, and rotate terminals in the client's world again (?). Thanks to Tim (tpr) for the bug report! See: https://lists.squeakfoundation.org/archives/list/squeak-dev@lists.squeakfou… =============== Diff against Nebraska-dtl.61 =============== Item was changed: ----- Method: NetworkTerminalMorph>>handleKeyDown: (in category 'events-processing') ----- handleKeyDown: anEvent anEvent wasHandled ifTrue:[^self]. (self handlesKeyboard: anEvent) ifFalse:[^self]. anEvent wasHandled: true. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.! Item was changed: ----- Method: NetworkTerminalMorph>>handleKeyUp: (in category 'events-processing') ----- handleKeyUp: anEvent anEvent wasHandled ifTrue:[^self]. (self handlesKeyboard: anEvent) ifFalse:[^self]. anEvent wasHandled: true. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.! Item was changed: ----- Method: NetworkTerminalMorph>>handleKeystroke: (in category 'events-processing') ----- handleKeystroke: anEvent anEvent wasHandled ifTrue:[^self]. anEvent wasHandled: true. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.! Item was changed: ----- Method: NetworkTerminalMorph>>handleMouseDown: (in category 'events-processing') ----- handleMouseDown: anEvent anEvent wasHandled ifTrue:[^self]. anEvent hand removePendingBalloonFor: self. anEvent hand removePendingHaloFor: self. anEvent wasHandled: true. anEvent hand newMouseFocus: self event: anEvent. anEvent hand removeHaloFromClick: anEvent on: self. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.! Item was changed: ----- Method: NetworkTerminalMorph>>handleMouseMove: (in category 'events-processing') ----- handleMouseMove: anEvent anEvent wasHandled ifTrue:[^self]. "not interested" (anEvent hand hasSubmorphs) ifTrue:[^self]. (anEvent anyButtonPressed and:[anEvent hand mouseFocus ~~ self]) ifTrue:[^self]. anEvent wasHandled: true. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.! Item was changed: ----- Method: NetworkTerminalMorph>>handleMouseUp: (in category 'events-processing') ----- handleMouseUp: anEvent anEvent wasHandled ifTrue:[^self]. "not interested" anEvent hand mouseFocus == self ifFalse:[^self]. "Not interested in other parties" anEvent hand releaseMouseFocus: self. anEvent wasHandled: true. + self sendEvent: anEvent.! - self sendEventAsIs: anEvent.!

1 0

The Inbox: Nebraska-ct.60.mcz
by commits＠source.squeak.org 26 Dec '23

26 Dec '23

Christoph Thiede uploaded a new version of Nebraska to project The Inbox: http://source.squeak.org/inbox/Nebraska-ct.60.mcz ==================== Summary ==================== Name: Nebraska-ct.60 Author: ct Time: 26 December 2023, 6:12:31.497645 pm UUID: 16f779fe-17ab-9040-8377-aa17b31b9297 Ancestors: Nebraska-mt.59 Fixes default port selection for Nebraska connections. Thanks to Tim (tpr) for the bug report! See: https://lists.squeakfoundation.org/archives/list/squeak-dev@lists.squeakfou… =============== Diff against Nebraska-mt.59 =============== Item was changed: ----- Method: NebraskaServer class>>serveWorld: (in category 'instance creation') ----- serveWorld: aWorld + ^self serveWorld: aWorld onPort: self defaultPort! - ^self serveWorld: aWorld onPort: self defaultPorts! Item was changed: ----- Method: NebraskaServerMorph class>>serveWorld: (in category 'as yet unclassified') ----- serveWorld: aWorld "Check to make sure things won't crash. See Mantis #0000519" ^aWorld isSafeToServe ifTrue:[ + self serveWorld: aWorld onPort: NebraskaServer defaultPort] - self serveWorld: aWorld onPort: NebraskaServer defaultPorts] !

1 0

BooleanArray?
by christoph.thiede＠student.hpi.uni-potsdam.de 26 Dec '23

26 Dec '23

Hi all, just curious: Could there be a ultrafast and efficient BooleanArray or BitArray that subclasses from RawBitsArray, analogously to ByteArray et al.? With bytesPerElement ^ 1 / 8 and VM-supported conversion to ByteArray et al.? So far I only found Yoshiki's old BitArray from 2003 on SqueakMap, which uses a Bitmap internally and has some failing tests. No actual need at the moment, just curious. And I think a modern implementation of that would be great to play with in the Trunk. :-) Best, Christoph --- Sent from Squeak Inbox Talk

4 5

The Trunk: Regex-Tests-Core-mt.35.mcz
by commits＠source.squeak.org 26 Dec '23

26 Dec '23

Marcel Taeumel uploaded a new version of Regex-Tests-Core to project The Trunk: http://source.squeak.org/trunk/Regex-Tests-Core-mt.35.mcz ==================== Summary ==================== Name: Regex-Tests-Core-mt.35 Author: mt Time: 21 December 2023, 5:11:41.06102 pm UUID: 26ba76e8-4b6e-6149-91f7-112ce481f547 Ancestors: Regex-Tests-Core-mt.34 Now that we had an extra checkpoint in the update map, this clean-up of Regex tests should actually work. Revive #testBackQuotesEscape as expected failure. Is this okay? =============== Diff against Regex-Tests-Core-mt.34 =============== Item was removed: - ----- Method: RxParserTest>>DoesNotWorktestBackQuotesEscape (in category 'tests') ----- - DoesNotWorktestBackQuotesEscape - "self debug: #testBackQuotesEscape" - - "Regular expressions can also include the following backquote escapes - to refer to popular classes of characters: - \w any word constituent character (same as [a-zA-Z0-9:=]) - \W any character but a word constituent - \d a digit (same as [0-9]) - \D anything but a digit - \s a whitespace character - \S anything but a whitespace character - These escapes are also allowed in character classes: '[\w+-]' means - 'any character that is either a word constituent, or a plus, or a - minus'." - - self assert: ('one word' matchesRegex: '\w'). - - self assert: ('one' matchesRegex: '\w'). - ! Item was changed: ----- Method: RxParserTest>>expectedFailures (in category 'failures') ----- expectedFailures + ^ #(testBackQuotesEscape)! - ^ #(testOptionalLookbehind2)! Item was added: + ----- Method: RxParserTest>>testBackQuotesEscape (in category 'tests') ----- + testBackQuotesEscape + "self debug: #testBackQuotesEscape" + + "Regular expressions can also include the following backquote escapes + to refer to popular classes of characters: + \w any word constituent character (same as [a-zA-Z0-9:=]) + \W any character but a word constituent + \d a digit (same as [0-9]) + \D anything but a digit + \s a whitespace character + \S anything but a whitespace character + These escapes are also allowed in character classes: '[\w+-]' means + 'any character that is either a word constituent, or a plus, or a + minus'." + + self assert: ('one word' matchesRegex: '\w'). + + self assert: ('one' matchesRegex: '\w'). + ! Item was removed: - ----- Method: RxParserTest>>testOptionalLookbehind2 (in category 'tests') ----- - testOptionalLookbehind2 - - self assert: [('AB' allRegexMatches: '((?<=a)b)?') asArray = #('A')].! Item was removed: - ----- Method: RxParserTest>>toDotestSpecialCharacterInSetRange (in category 'tests') ----- - toDotestSpecialCharacterInSetRange - "self debug: #testSpecialCharacterInSetRange" - - "Special characters within a set are `^', `-', and `]' that closes the - set. Below are the examples of how to literally use them in a set: - [01^] -- put the caret anywhere except the beginning - [01-] -- put the dash as the last character - []01] -- put the closing bracket as the first character - [^]01] (thus, empty and universal sets cannot be specified)" - - self assert: ('0' matchesRegex: '[01^]'). - - self assert: ('0' matchesRegex: '[0-9]'). - !

2 1

Message senders in OOP
by Jaromir Matas 26 Dec '23

26 Dec '23

Hi, OOP lectures usually begin with: "Objects communicate by sending messages to each other." BUT: have you ever seen something like: `senderObject sendMessageTo: receiverObject` ??? Instead, it's always like: `receiverObject receiveMessageWithOrWithoutArguments: args` QUESTION: Who is the "sender" actually? I've heard/found three "opinions": (1) `self` (aka `this`) (2) context/closure where the send happens (3) the programmer :) Do we ever care about senders? Is knowledge about senders relevant in some way in writing code? (Note: message "senders" are not to be confused with context chain's senders.) Although I tend to agree with (1), you hear so often: "You send a message to an object [...]" that (3) almost sounds like an implicit understanding (unless, of course, "you" are meant to step into self's shoes). Ok, back to serious work :) Merry Christmas, Jaromir -- Jaromir Matas mail(a)jaromir.net

5 9

The Inbox: Morphic-ct.2135.mcz
by commits＠source.squeak.org 21 Dec '23

21 Dec '23

Christoph Thiede uploaded a new version of Morphic to project The Inbox: http://source.squeak.org/inbox/Morphic-ct.2135.mcz ==================== Summary ==================== Name: Morphic-ct.2135 Author: ct Time: 21 December 2023, 7:28:06.112529 pm UUID: 89fd1e6d-3439-8449-a60e-46780e9e55a2 Ancestors: Morphic-eem.2133 Avoids redundant damage recording from transform morphs. For instance, hovering over an indenting list item in a tree browser caused damages in the half width of the screen (cf. debugShowDamage). Nevertheless, I could not measure any significant performance increase in many-window-scenarios. Please review. =============== Diff against Morphic-eem.2133 =============== Item was changed: ----- Method: TransformMorph>>invalidRect:from: (in category 'change reporting') ----- invalidRect: damageRect from: aMorph "Translate damage reports from submorphs by the scrollOffset." ^ super invalidRect: (aMorph == self ifTrue: [damageRect] ifFalse: [(transform localBoundsToGlobal: damageRect) expanded]) + from: aMorph! - from: self!

1 0

The Trunk: Graphics-mt.549.mcz
by commits＠source.squeak.org 21 Dec '23

21 Dec '23

Marcel Taeumel uploaded a new version of Graphics to project The Trunk: http://source.squeak.org/trunk/Graphics-mt.549.mcz ==================== Summary ==================== Name: Graphics-mt.549 Author: mt Time: 8 December 2023, 9:44:03.724103 am UUID: d73c6d39-cf42-6549-9068-c9f2201aeb9b Ancestors: Graphics-dtl.548 Expand commentary for #px, now that I realized that mixed-arithmetic is the reason why float*int is faster than int*float. Might still be a bug in the VM though. =============== Diff against Graphics-dtl.548 =============== Item was changed: ----- Method: Number>>px (in category '*Graphics-scale factor') ----- px "Convert the receiver representing raw pixels at 100% (96ppi) to the current scale factor. Note that you currently have to do this manually for all graphics-related properties and layout-specific measures such as #borderWidth: and #layoutInset:. Only for model windows (see #initialExtent) that are no dialogs, that scaling will happen automatically in ToolBuilder." | scaleFactor | self = 0 ifTrue: [^ self]. (scaleFactor := RealEstateAgent scaleFactor) = 1 ifTrue: [^ self]. ^ self > 4 ifTrue: [(scaleFactor * self) rounded] ifFalse: [(scaleFactor * self) truncated] + "For self > 4, we recommend #rounded instead of #truncated. For smaller values, however, rounding makes no sense because we have no sub-pixel access and things would look too big too soon. Also, #scaleFactor might be a float and self is usually an integer. Thus, self should be on the right side of the multiplication to speed up the whole thing...because mixed-arithmetic seems to only be optimized this way around."! - "For self > 4, we recommend #rounded instead of #truncated. For smaller values, however, rounding makes no sense because we have no sub-pixel access and things would look too big too soon. Also, #scaleFactor might be a float and self is usually an integer. Thus, self should be on the right side of the multiplication to speed up the whole thing."!

5 8

The Inbox: Kernel-mt.1545.mcz
by commits＠source.squeak.org 21 Dec '23

21 Dec '23

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-mt.1545.mcz ==================== Summary ==================== Name: Kernel-mt.1545 Author: mt Time: 21 December 2023, 5:35:58.67902 pm UUID: fcde1fb1-0264-7a40-9117-67d9fdd740de Ancestors: Kernel-mt.1544 Propose different fallback for mixed int-float arithmetics to use VM-backed mixed float-int arithmetics for + - * / . Speed-up is about 7x on my machine. =============== Diff against Kernel-mt.1544 =============== Item was changed: ----- Method: SmallInteger>>* (in category 'arithmetic') ----- * aNumber "Primitive. Multiply the receiver by the argument and answer with the result if it is a SmallInteger. Fail if the argument or the result is not a SmallInteger. Essential. No Lookup. See Object documentation whatIsAPrimitive." <primitive: 9> + ^ aNumber isFloat + ifTrue: [aNumber * self "exploit mixed arithmetic in float primitives"] + ifFalse: [super * aNumber]! - ^ super * aNumber! Item was changed: ----- Method: SmallInteger>>+ (in category 'arithmetic') ----- + aNumber "Primitive. Add the receiver to the argument and answer with the result if it is a SmallInteger. Fail if the argument or the result is not a SmallInteger Essential No Lookup. See Object documentation whatIsAPrimitive." <primitive: 1> + ^ aNumber isFloat + ifTrue: [aNumber + self "exploit mixed arithmetic in float primitives"] + ifFalse: [super + aNumber]! - ^ super + aNumber! Item was changed: ----- Method: SmallInteger>>- (in category 'arithmetic') ----- - aNumber "Primitive. Subtract the argument from the receiver and answer with the result if it is a SmallInteger. Fail if the argument or the result is not a SmallInteger. Essential. No Lookup. See Object documentation whatIsAPrimitive." <primitive: 2> + ^ aNumber isFloat + ifTrue: [aNumber negated + self "exploit mixed arithmetic in float primitives"] + ifFalse: [super - aNumber]! - ^super - aNumber! Item was changed: ----- Method: SmallInteger>>/ (in category 'arithmetic') ----- / aNumber "Primitive. This primitive (for /) divides the receiver by the argument and returns the result if the division is exact. Fail if the result is not a whole integer. Fail if the argument is 0 or is not a SmallInteger. Optional. No Lookup. See Object documentation whatIsAPrimitive." <primitive: 10> + ^ aNumber isFloat + ifTrue: [(1.0 / aNumber) * self "exploit mixed arithmetic in float primitives"] + ifFalse: [super / aNumber]! - ^super / aNumber!

1 0

The Trunk: Regex-Tests-Core-mt.34.mcz
by commits＠source.squeak.org 21 Dec '23

21 Dec '23

Marcel Taeumel uploaded a new version of Regex-Tests-Core to project The Trunk: http://source.squeak.org/trunk/Regex-Tests-Core-mt.34.mcz ==================== Summary ==================== Name: Regex-Tests-Core-mt.34 Author: mt Time: 15 December 2023, 2:55:54.123424 pm UUID: 053ecc9e-66fc-2b4b-a29a-c03b4b4a8ab1 Ancestors: Regex-Tests-Core-ct.33 Some test selectors seem to be missing... maybe a prior version was incomplete? Try to fix this. =============== Diff against Regex-Tests-Core-ct.33 =============== Item was added: + ----- Method: RxParserTest>>expectedFailures (in category 'failures') ----- + expectedFailures + + ^ #(testOptionalLookbehind2)! Item was added: + ----- Method: RxParserTest>>testOptionalLookbehind2 (in category 'tests') ----- + testOptionalLookbehind2 + + self assert: [('AB' allRegexMatches: '((?<=a)b)?') asArray = #('A')].! Item was added: + ----- Method: RxParserTest>>toDotestSpecialCharacterInSetRange (in category 'tests') ----- + toDotestSpecialCharacterInSetRange + "self debug: #testSpecialCharacterInSetRange" + + "Special characters within a set are `^', `-', and `]' that closes the + set. Below are the examples of how to literally use them in a set: + [01^] -- put the caret anywhere except the beginning + [01-] -- put the dash as the last character + []01] -- put the closing bracket as the first character + [^]01] (thus, empty and universal sets cannot be specified)" + + self assert: ('0' matchesRegex: '[01^]'). + + self assert: ('0' matchesRegex: '[0-9]'). + !

4 5

← Newer
1
2
3
4
5
6
7
8
9
...
13
Older →