Squeak-dev September 2017

squeak-dev@lists.squeakfoundation.org

30 participants
85 discussions

Start a nNew thread

IPv6 implementation code
by Alan Pinch 23 Sep '17

23 Sep '17

Could anyone be able to point me to working IPv6 code for squeak, please? I would appreciate any link. Alan

4 9

The Trunk: Tests-mt.384.mcz
by commits＠source.squeak.org 23 Sep '17

23 Sep '17

Marcel Taeumel uploaded a new version of Tests to project The Trunk: http://source.squeak.org/trunk/Tests-mt.384.mcz ==================== Summary ==================== Name: Tests-mt.384 Author: mt Time: 23 September 2017, 10:54:37.809102 am UUID: e04a490b-01cb-bc4d-aca8-76336e7ce5a4 Ancestors: Tests-mt.383 UI Themes: Updates tests and benchmark for the latest changes in System-mt.963. =============== Diff against Tests-mt.383 =============== Item was added: + ----- Method: UserInterfaceThemeTest>>test27DanglingTheme (in category 'tests') ----- + test27DanglingTheme + + self + assert: (UserInterfaceTheme allThemes includes: UserInterfaceTheme current) + description: 'The current user interface theme is not registered.'.! Item was removed: - ----- Method: UserInterfaceThemeTest>>test27ScopeIntegrity (in category 'tests') ----- - test27ScopeIntegrity - "If application code manages to use Object >> #userInterfaceTheme without invoking the DNU dispatch directly afterwards, the theme's scope might get inconsistent. Even though this should usually never happen, check for it to be sure." - - | issues | - issues := OrderedCollection new. - UserInterfaceTheme allThemes do: [:uit | - (uit instVarNamed: #scope) isEmpty ifFalse: [issues add: uit]]. - UserInterfaceTheme current in: [:uit | - (UserInterfaceTheme allThemes includes: uit) - ifFalse: [(uit instVarNamed: #scope) isEmpty ifFalse: [issues add: uit]]]. - self assert: issues isEmpty description: 'Some user interface themes have an inconsistent scope state, which can interfere with GC.'.! Item was removed: - ----- Method: UserInterfaceThemeTest>>test28DanglingTheme (in category 'tests') ----- - test28DanglingTheme - - self - assert: (UserInterfaceTheme allThemes includes: UserInterfaceTheme current) - description: 'The current user interface theme is not registered.'.! Item was changed: ----- Method: UserInterfaceThemeTestObject class>>benchLookup (in category 'benchmark') ----- benchLookup " + Microsoft Surface Pro 3, Windows 10 v1703, CogVM 201708092224, Squeak 6.0alpha #17398 + Up to '280,000 per second. 3.57 microseconds per run.' -- leaves enough room for quirky morphs that keep on drawing themselves based on direct theme lookup. - Microsoft Surface Pro 3, Windows 10 v1511, CogVM r201606301459, Squeak 5.1alpha #16138 - '210,000 per second. 4.76 microseconds per run.' -- leaves enough room for quirky morphs that keep on drawing themselves based on direct theme lookup. I think this setup is really heavy. Morphs should not look-up things that often. They can cache. Anyway: - link through 3 themes - look up superclasses up to ProtoObject (for each theme!!) self benchLookup" | c t1 t2 t3 m result | c := UserInterfaceTheme current. m := UserInterfaceThemeTestObject new. t1 := UserInterfaceTheme new name: #benchmarkOne. t2 := UserInterfaceTheme new name: #benchmarkTwo. t3 := UserInterfaceTheme new name: #benchmarkThree. t3 set: #testColor for: ProtoObject to: Color white. t1 link: t2. t2 link: t3. t1 apply. result := OrderedCollection new. [ + 3 timesRepeat: [ + Smalltalk garbageCollect. + result add: [m getTestColor] bench]. - 3 timesRepeat: [result add: [m getTestColor] bench]. ] ensure: [c apply]. result explore.!

1 0

The Trunk: System-mt.963.mcz
by commits＠source.squeak.org 23 Sep '17

23 Sep '17

Marcel Taeumel uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-mt.963.mcz ==================== Summary ==================== Name: System-mt.963 Author: mt Time: 23 September 2017, 10:47:56.940596 am UUID: d6e13c37-16d6-c34b-a3cf-64afaf4cfaba Ancestors: System-tpr.962 Removes "scope" from UI themes. Encapsulates look-up for properties in the current theme into short-living a request object. Why? 1. Dispels some magic from UserInterfaceTheme class. 2. Supports keeping reference to the result of "self userInterfaceTheme" without annoying the GC. 3. Speeds up look-up performance by up to 5%. =============== Diff against System-tpr.962 =============== Item was changed: ----- Method: Object>>userInterfaceTheme (in category '*System-Preferences') ----- userInterfaceTheme "Call this to conveniently access properties from the current user interface theme." + ^ UserInterfaceThemeRequest new + target: self; + theme: UserInterfaceTheme current; - ^ UserInterfaceTheme current - pushScope: self; yourself! Item was changed: Object subclass: #UserInterfaceTheme + instanceVariableNames: 'properties name next ignoreApply lastScaleFactor' - instanceVariableNames: 'scope properties name next ignoreApply lastScaleFactor' classVariableNames: 'All Current Default' poolDictionaries: '' category: 'System-Support'! !UserInterfaceTheme commentStamp: '<historical>' prior: 0! A UserInterfaceTheme is a dictionary of preferred visual-properties; colors, borderStyles, borderWidths, fonts, forms, etc. used to color and style the IDE. Accessing The Theme To access the proper UserInterfaceTheme instance for an object, send it #userInterfaceTheme. The default implementation on Object provides the one instance of that is in-use by the IDE at the current time. Customizing The Theme We can ask the userInterfaceTheme for the value of any visual-property, by name: mySystemWindow userInterfaceTheme closeBoxImage Initially, the above answers nil, which causes the legacy code to use whatever default it's always used. To override various visual-properties of any kind of object, the #set: onAny: to: message can be used. For example, myUserInterfaceTheme set: #closeBoxImage for: SystemWindow to: MenuIcons smallCancelIcon Alternatively, values may be derived based on other values in the theme, as in: myUserInterfaceTheme set: #color for: FillInTheBlankMorph to: { MenuMorph->#color. #twiceDarker } Now, the accessing expression, above, will answer will answer MenuIcons' smallCancelIcon instead of nil. SystemWindow's code can be changed to use the expression above to access elements of the theme. Upgrading Legacy Code Following the introduction of this class, various client code all around the system must be modified to access it. This variety of legacy code uses a variety of methods to specify their visual properties: 1) a hard-coded values. 2) a values derived from some other value. 3) providing local storage for a settable value which can be nil. 4) providing local storage for a settable value which is expected to always have a particular valid value (never nil). The requirement, for each case, is to let the value be overridden. The solution for each of the above should be handled respectively to the above list, as follows: 1) Check the userInterfaceTheme, if that property returns nil, use the legacy hard-coded value. (see example: SystemWindow>>#createCloseBox). 2) Nothing to do -- simply perform the same derivation on the result of (1). 3) Check the local storage, if present, use it. If nil, then check the userInterfaceTheme, if it has this property present, use it, else return nil. 4) Check the userInterfaceTheme, if the property is not nil, use it, otherwise use the local value. Tool Support If a new access to #userInterfaceTheme is added to the code, be sure to add the property and its description to the #themeSettings for that class. See implementors of #themeSettings for examples.! Item was removed: - ----- Method: UserInterfaceTheme>>doesNotUnderstand: (in category 'lookup') ----- - doesNotUnderstand: aMessage - "In order to be able to use a UserInterfaceTheme as a container of fairly arbitrary properties whilst making it seem like we are sending regular messages as a way of accessing those properties we can handle the dNU: and check the not understood message name against our property list. This is clever, devious, interesting and may confuse users until they get to see an explanation like this" - "Answer nil or a value for the property specified by aMessage's #selector. Searching for the property proceeds by - a) searching my dictionary for a key made up of an Association with a key of the class of the 'client' and a value of the message name. For example SimpleButtonMorph->borderColor - b) searching again for a key made from the superclass(es) of the client - e.g. RectangleMorph->borderColor and then if required BorderedMorph->borderColor etc. - c) if there is a linked theme, search it in the same manner. - - As an extreme example, consider a basic theme with a linked theme specifically for buttons. - mySimpleButtonMorph borderColor - would search the basic theme for SimpleButtonMorph->borderColor, the superclass equivalents as in b) above, then search the linked theme for SimpleButtonMorph->borderColor and, we hope, find something meaningful" - - aMessage numArgs > 0 ifTrue: [^ super doesNotUnderstand: aMessage]. - scope isEmpty ifTrue: [^ super doesNotUnderstand: aMessage]. - - ^ [self get: scope top class -> aMessage selector] - ensure: [scope pop]! Item was changed: ----- Method: UserInterfaceTheme>>initialize (in category 'initialization') ----- initialize super initialize. name := 'unnamed'. + properties := Dictionary new.! - properties := Dictionary new. - scope := Stack new! Item was changed: ----- Method: UserInterfaceTheme>>postCopy (in category 'copying') ----- postCopy "Keep same name and linked next." super postCopy. + properties := properties copy.! - properties := properties copy. - scope := nil! Item was removed: - ----- Method: UserInterfaceTheme>>pushScope: (in category 'private') ----- - pushScope: anObject - scope push: anObject! Item was added: + Object subclass: #UserInterfaceThemeRequest + instanceVariableNames: 'target theme' + classVariableNames: '' + poolDictionaries: '' + category: 'System-Support'! + + !UserInterfaceThemeRequest commentStamp: 'mt 9/23/2017 10:37' prior: 0! + In order to be able to use a UserInterfaceTheme as a container of fairly arbitrary properties whilst making it seem like we are sending regular messages as a way of accessing those properties we can handle the dNU: and check the not understood message name against our property list. This is clever, devious, interesting and may confuse users until they get to see an explanation like this. + + Answer nil or a value for the property specified by aMessage's #selector. Searching for the property proceeds by + a) searching my dictionary for a key made up of an Association with a key of the class of the 'client' and a value of the message name. For example SimpleButtonMorph->borderColor + b) searching again for a key made from the superclass(es) of the client - e.g. RectangleMorph->borderColor and then if required BorderedMorph->borderColor etc. + c) if there is a linked theme, search it in the same manner. + + As an extreme example, consider a basic theme with a linked theme specifically for buttons. + + mySimpleButtonMorph borderColor + + ... would search the basic theme for SimpleButtonMorph->borderColor, the superclass equivalents as in b) above, then search the linked theme for SimpleButtonMorph->borderColor and, we hope, find something meaningful.! Item was added: + ----- Method: UserInterfaceThemeRequest>>doesNotUnderstand: (in category 'lookup') ----- + doesNotUnderstand: aMessage + "Look up the visual-attribute specified by aMessage's #selector in the current theme for the current target object." + + ^ aMessage numArgs = 0 + ifTrue: [self theme get: self target class -> aMessage selector] + ifFalse: [super doesNotUnderstand: aMessage]! Item was added: + ----- Method: UserInterfaceThemeRequest>>target (in category 'accessing') ----- + target + + ^ target + ! Item was added: + ----- Method: UserInterfaceThemeRequest>>target: (in category 'accessing') ----- + target: anObject + + target := anObject. + ! Item was added: + ----- Method: UserInterfaceThemeRequest>>theme (in category 'accessing') ----- + theme + + ^ theme + ! Item was added: + ----- Method: UserInterfaceThemeRequest>>theme: (in category 'accessing') ----- + theme: anObject + + theme := anObject. + !

1 0

The Trunk: System-tpr.962.mcz
by commits＠source.squeak.org 22 Sep '17

22 Sep '17

tim Rowledge uploaded a new version of System to project The Trunk: http://source.squeak.org/trunk/System-tpr.962.mcz ==================== Summary ==================== Name: System-tpr.962 Author: tpr Time: 18 September 2017, 4:45:22.01173 pm UUID: e1c54891-6fa2-45fd-9acb-58c76815aa62 Ancestors: System-dtl.961 Add and expand some comments that should help to explain UserInterfaceTheme for future readers =============== Diff against System-dtl.961 =============== Item was changed: ----- Method: UserInterfaceTheme>>doesNotUnderstand: (in category 'lookup') ----- + doesNotUnderstand: aMessage + "In order to be able to use a UserInterfaceTheme as a container of fairly arbitrary properties whilst making it seem like we are sending regular messages as a way of accessing those properties we can handle the dNU: and check the not understood message name against our property list. This is clever, devious, interesting and may confuse users until they get to see an explanation like this" + "Answer nil or a value for the property specified by aMessage's #selector. Searching for the property proceeds by + a) searching my dictionary for a key made up of an Association with a key of the class of the 'client' and a value of the message name. For example SimpleButtonMorph->borderColor + b) searching again for a key made from the superclass(es) of the client - e.g. RectangleMorph->borderColor and then if required BorderedMorph->borderColor etc. + c) if there is a linked theme, search it in the same manner. + + As an extreme example, consider a basic theme with a linked theme specifically for buttons. + mySimpleButtonMorph borderColor + would search the basic theme for SimpleButtonMorph->borderColor, the superclass equivalents as in b) above, then search the linked theme for SimpleButtonMorph->borderColor and, we hope, find something meaningful" - doesNotUnderstand: aMessage - "Answer whether I have, or inherit, a value for the visual-attribute specified by aMessage's #selector." aMessage numArgs > 0 ifTrue: [^ super doesNotUnderstand: aMessage]. scope isEmpty ifTrue: [^ super doesNotUnderstand: aMessage]. ^ [self get: scope top class -> aMessage selector] ensure: [scope pop]! Item was changed: ----- Method: UserInterfaceTheme>>get: (in category 'private') ----- get: keyObject + "keyObject is intended to be an Association. We have two lookup strategies: 1) along the superclass chain *of the client*, 2) via a linked theme. Evaluate the result because there can be message sends stored or blocks." - "keyObject is intended to be an Association. We have two lookup strategies: 1) along the superclass chain, 2) via a linke theme. Evaluate the result because there can be message sends stored or blocks." | k | properties at: keyObject ifPresent: [:prop | ^ prop value]. keyObject isVariableBinding "simple key objects" ifFalse: [^ self getViaLink: keyObject]. k := keyObject key. (self getViaSuperclasses: keyObject) ifNotNil: [:prop | ^ prop]. keyObject key: k. "restore" ^ self getViaLink: keyObject! Item was changed: ----- Method: UserInterfaceTheme>>getViaLink: (in category 'private') ----- getViaLink: keyObject + "keyObject is intended to be an Association. + If there is a linked theme, see if it has the relevant property available" - "keyObject is intended to be an Association" ^ next ifNotNil: [next get: keyObject]! Item was changed: ----- Method: UserInterfaceTheme>>getViaSuperclasses: (in category 'private') ----- getViaSuperclasses: keyObject + "keyObject is intended to be an Association. + Find the superclass of the key of the keyObject (which will initially be the client's class) and make a new keyObject using that and the original message name, then try searching for that." - "keyObject is intended to be an Association" "We know we're the only referencer of keyObject. Update it rather than create new ones, for performance reasons." keyObject key: keyObject key superclass. keyObject key ifNil: [^ nil]. properties at: keyObject ifPresent: [:prop | ^ prop value]. ^ self getViaSuperclasses: keyObject!

6 7

Re: [squeak-dev] VersionNumber disallows zeros.
by Jakob Reschke 22 Sep '17

22 Sep '17

What is the current behavior if two branched version numbers are compared? true, false, error? I would say they are not comparable anyway. What do you want to know? "Can I upgrade to get an increment?" "Can I upgrade without breaking some API?" "Which is newer?" All of these cannot be answered without additional information about the versioning scheme (e.g., in SemVer you could answer the first two queries, but not the third without an additional timestamp). And these queries should have their own messages instead of a general-purpose comparison. Kind regards, Jakob Am 21.09.2017 08:44 schrieb "Taeumel, Marcel" <Marcel.Taeumel(a)hpi.de>: > Hi Tobias, > > I see several issues with the current implementation of VersionNumber. :) > > - You cannot compare 4.1 to 3.1 because such branches are treated > unordered. > - You cannot even compare 4.1.1 to 4.2.1 for the same reason. But you can > compare 4.1 to 4.2 though. > > This logic might be the reason to throw out the zero all together: 4.1 and > 4.1.0 are not so different, yet the first will be comparable but the second > will not. That "branch logic" seems to be the key. Try changing > #initializeNumbers: to accept zero and then play around with the comparison > logic. > > It's kind of weird or at least incomprehensible. I cannot find useful > comments either. > > Best, > Marcel > > Am 20.09.2017 20:34:36 schrieb Tobias Pape <das.linux(a)gmx.de>: > Hi, > > what's the rationale of VersionNumber prohibiting zeros in any of the > version parts? > Eg, 4.0.3 is not a valid VersionNumber currently. > > Best regards > -Tobias > >

7 9

VersionNumber disallows zeros.
by Tobias Pape 21 Sep '17

21 Sep '17

Hi, what's the rationale of VersionNumber prohibiting zeros in any of the version parts? Eg, 4.0.3 is not a valid VersionNumber currently. Best regards -Tobias

2 1

CallistoHouse plans and specs
by Alan Pinch 20 Sep '17

20 Sep '17

Here are the business plans and specs for CallistoHouse. Love any feedback. http://jmp.sh/kMERqAl -- Thank you for your consideration, Alan

1 0

Re: [squeak-dev] ASN1 encoding of UTF8
by Jakob Reschke 20 Sep '17

20 Sep '17

2017-09-20 21:42 GMT+02:00 Alan Pinch <alan.c.pinch(a)gmail.com>: > Would anyone have some interesting utf8 bytes > handy? http://xahlee.info/comp/unicode_drawing_shapes.html :-) 🐭 ┃┣━━━┳━━━━┳━━┓ ┃┗┓┏┛┃╻╺━━┛╺┓┃ ┣┓┃┗┓┗┻━━━┳╸┃┃ ┃┃┣╸┣━━┳━┓┗━┛┃ ┃┃┃┏┛┏╸┃╻┣━┳╸┃ ┃┗━┫╻┣━━┫┗╸┃┏┫ ┃┏━┫┃┃╺┓┗━┓┃┃┃ ┃┃┃┃┃┗┓┗━┓┗┻╸┃ ┗━┫┏┻━━━━┻━━━┛ Can be copy&pasted into a workspace. You only get to see question marks, but the character values are correct. theAbove squeakToUtf8 asByteArray => #[226 148 131 226 148 163 226 148 129 226 148 129 226 148 129 226 148 179 226 148 129 226 148 129 226 148 129 226 148 129 226 148 179 226 148 129 226 148 129 226 148 147 13 226 148 131 226 148 151 226 148 147 226 148 143 226 148 155 226 148 131 226 149 187 226 149 186 226 148 129 226 148 129 226 148 155 226 149 186 226 148 147 226 148 131 13 226 148 163 226 148 147 226 148 131 226 148 151 226 148 147 226 148 151 226 148 187 226 148 129 226 148 129 226 148 129 226 148 179 226 149 184 226 148 131 226 148 131 13 226 148 131 226 148 131 226 148 163 226 149 184 226 148 163 226 148 129 226 148 129 226 148 179 226 148 129 226 148 147 226 148 151 226 148 129 226 148 155 226 148 131 13 226 148 131 226 148 131 226 148 131 226 148 143 226 148 155 226 148 143 226 149 184 226 148 131 226 149 187 226 148 163 226 148 129 226 148 179 226 149 184 226 148 131 13 226 148 131 226 148 151 226 148 129 226 148 171 226 149 187 226 148 163 226 148 129 226 148 129 226 148 171 226 148 151 226 149 184 226 148 131 226 148 143 226 148 171 13 226 148 131 226 148 143 226 148 129 226 148 171 226 148 131 226 148 131 226 149 186 226 148 147 226 148 151 226 148 129 226 148 147 226 148 131 226 148 131 226 148 131 13 226 148 131 226 148 131 226 148 131 226 148 131 226 148 131 226 148 151 226 148 147 226 148 151 226 148 129 226 148 147 226 148 151 226 148 187 226 149 184 226 148 131 13 226 148 151 226 148 129 226 148 171 226 148 143 226 148 187 226 148 129 226 148 129 226 148 129 226 148 129 226 148 187 226 148 129 226 148 129 226 148 129 226 148 155] Alternatively, you could try some pseudo-German pseudo-names like: 'Björn-Thaddäus Düngerstraß' squeakToUtf8 asByteArray => #[66 106 195 182 114 110 45 84 104 97 100 100 195 164 117 115 32 68 195 188 110 103 101 114 115 116 114 97 195 159]. > > ASN1UTF8StringType > > >>#encodeValue: anObject withDERStream: derStream > > derStream nextPutAll: anObject squeakToUtf8 asByteArray > > >>#decodeValueWithDERStream: derStream length: length > > ^ (derStream next: length) asByteArray asString utf8ToSqueak. > > CryptoASN1Test>>#testConstructedUTF8String > > | bytes obj testObj | > bytes := #(44 15 12 5 84 101 115 116 32 12 6 85 115 101 114 32 49). > testObj := 'Test User 1'. > obj := ASN1InputStream decodeBytes: bytes. > self assert: (obj = testObj). > > Thank you for your consideration, > Alan > > > On 09/18/2017 12:29 PM, tim Rowledge wrote: >> We do have assorted string encoding stuff in the current image but the actual UTF8 results of #squeakToUtf8 (for example) are just ByteStrings. Which is actually rather confusing and annoying because now you have no way to know what encoding is relevant other than be carefully keeping track manually. Normally of course, within the image we have perfectly usable strings because any time a unicode character that is outside the 1-byte range is used the string becomes a WideString. >> >> We need to do better. Look at TextEncoder and its hierarchy for more info. >> >> tim >> -- >> tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim >> Strange OpCodes: RLBM: Ruin Logic Board Multiple >> >> >> > >

2 2

The Trunk: Morphic-mt.1350.mcz
by commits＠source.squeak.org 20 Sep '17

20 Sep '17

Marcel Taeumel uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mt.1350.mcz ==================== Summary ==================== Name: Morphic-mt.1350 Author: mt Time: 20 September 2017, 8:17:14.164191 pm UUID: a858e498-8304-9c48-a4d8-06e6fc226960 Ancestors: Morphic-tpr.1349 Fixes a mouse-focus bug that has revealed itself in the score player morph when changing the instruments for the tracks. Actually, we cannot just save/restore the moues focus for this modal dialog invocation. If that invocation comes after a mouse-down, it will mess up Morphic's assumption that there will be a mouse-up to clear the focus, which already happened in the above case. =============== Diff against Morphic-tpr.1349 =============== Item was changed: ----- Method: DialogWindow>>getUserResponse (in category 'running') ----- getUserResponse | hand world | (ProvideAnswerNotification signal: self message asString) ifNotNil: [:answer| ^ answer = #default ifTrue: [result] ifFalse: [answer]]. self message ifEmpty: [messageMorph delete]. "Do not waste space." self paneMorph submorphs ifEmpty: [self paneMorph delete]. "Do not waste space." + - hand := self currentHand. world := self currentWorld. + - self fullBounds. self center: preferredPosition. self bounds: (self bounds translatedToBeWithin: world bounds). self openInWorld: world. hand keyboardFocus in: [:priorKeyboardFocus | + self exclusive ifTrue: [hand newMouseFocus: self]. + hand newKeyboardFocus: self. - hand mouseFocus in: [:priorMouseFocus | - self exclusive ifTrue: [hand newMouseFocus: self]. - hand newKeyboardFocus: self. + [self isInWorld] whileTrue:[world doOneSubCycle]. - [self isInWorld] whileTrue:[world doOneSubCycle]. + hand newKeyboardFocus: priorKeyboardFocus. + hand releaseMouseFocus]. - hand newKeyboardFocus: priorKeyboardFocus. - self exclusive ifTrue: [ - hand newMouseFocus: priorMouseFocus]]]. ^ result!

1 0

The Trunk: 39Deprecated-fbs.20.mcz
by commits＠source.squeak.org 20 Sep '17

20 Sep '17

David T. Lewis uploaded a new version of 39Deprecated to project The Trunk: http://source.squeak.org/trunk/39Deprecated-fbs.20.mcz ==================== Summary ==================== Name: 39Deprecated-fbs.20 Author: fbs Time: 25 July 2012, 9:42:16.56 pm UUID: b22c5338-3200-4545-89bc-3f75c07e39af Ancestors: 39Deprecated-ar.19 These methods are deprecated, and I can find no uses in the base image. =============== Diff against 39Deprecated-ar.19 =============== Item was removed: - ----- Method: SharedQueue2>>flush (in category '*39Deprecated') ----- - flush - self deprecated: 'use removeAll'. - ^self removeAll! Item was removed: - ----- Method: SharedQueue2>>flushAllSuchThat: (in category '*39Deprecated') ----- - flushAllSuchThat: aBlock - self deprecated: 'use removeAllSuchThat:'. - - ^self removeAllSuchThat: aBlock!

5 7

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