Squeak-dev July 2022

squeak-dev@lists.squeakfoundation.org

33 participants
227 discussions

w=given a BaselineOf subclass successfully loaded, where does one find where it was loaded from?
by Eliot Miranda 25 Jul '22

25 Jul '22

Hi, I have code successfully loaded in one image that I'd like to load in another image. So I don't have the load scripts for the dependencies, I only have the load script for the outermost project. One of these dependencies is the PhaNAPI package. I'd like therefore to be able to load whereever BaselineOfPhaNAPI came from. If I have class BaselineOfPhaNAPI, how do I ask it the url from which it was loaded? _,,,^..^,,,_ best, Eliot

2 1

The Inbox: Kernel-ct.1487.mcz
by commits＠source.squeak.org 25 Jul '22

25 Jul '22

A new version of Kernel was added to project The Inbox: http://source.squeak.org/inbox/Kernel-ct.1487.mcz ==================== Summary ==================== Name: Kernel-ct.1487 Author: ct Time: 23 July 2022, 5:04:54.100611 pm UUID: 7b5df1b4-09a6-cd43-a466-9984c0bf96fb Ancestors: Kernel-eem.1486 Fixes a bug in simulation of primitive 188. The nested #doPrimitive:... send must be passed the methodArg that was passed along with primitive 188, not the the original method that has called the primitive. This seems to be a regression from Kernel-eem.1205. =============== Diff against Kernel-eem.1486 =============== 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 number of arguments']. 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 ifTrue: "Object>>withArgs:executeMethod: CompiledMethod class>>receiver:withArguments:executeMethod: VMMirror>>ifFail:object:with:executeMethod: et al" [| n args methodArg thisReceiver | ((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: methodArg receiver: thisReceiver args: 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]!

2 1

headful evaluation of script, supplied on the command line, with Squeak 6
by Eliot Miranda 24 Jul '22

24 Jul '22

Hi All, I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!). How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress? I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments: ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot

5 14

WeakIdentityDictionary vs WeakSet
by Stéphane Rollandin 24 Jul '22

24 Jul '22

Hello all, I noticed that a WeakIdentityDictionary does not hold literal values. For example, in a workspace: wd := WeakIdentityDictionary new. wd at: #foo put: 42. wd at: #bar put: #foo. wd "printIt ->" a WeakIdentityDictionary() On the other hand, WeakSet does hold literals ws := WeakSet new. ws add: #foo. ws add: 42. ws "printIt ->" a WeakSet(#foo 42) And also WeakKeyDictionary wk := WeakKeyDictionary new. wk at: #foo put: 42. wk at: #bar put: #foo. wk "printIt ->" a WeakKeyDictionary(#bar->#foo #foo->42 ) Is this the intended behavior? What is the semantics here? Stef

2 2

[Sounds] How to turn off reverb
by Thiede, Christoph 20 Jul '22

20 Jul '22

Hi all, I never have dealt with the Sound system in Squeak before so here is a newbie question from my side: How can I turn off the reverb which you hear every time you play an FM sound? Take this example: AbstractSound dial: '#'. Either my speakers are broken or there is a reverb that is hidden somewhere in the implementation of FMSound. :-) I can also reproduce this when creating an FMSound manually without defining any envelopes. I also took a look at the ingenious Speech-TTS package from Squeak 3 and could hear a reverb there, too. Is this a bug? Is this a - maybe unfortunate - default setting? How can I turn off this? Thanks in advance! :-) Best, Christoph

8 13

Low-space considerations ... :-)
by Marcel Taeumel 20 Jul '22

20 Jul '22

Hi all -- What's the current state of our low-space guards in Squeak? That OutOfMemory error only works with larger allocations, right? Our #lowSpaceWatcher seems to be broken because "Smalltalk specialObjectsArray at: 23" is always "nil". Should we replace it with "Processor preemptedProcecss"? Has #lowSpaceThreshold any effect these days? Has #primSignalAtBytesLeft: (primitive 125) any effect these days? Can there ever be an image-level protection against stack-page shortage? VM parameter 42 seems to be 50 (num stack pages), which lasts for quite some time in endless recursion ... but CMD+Dot stops working at some point because of some stack-growing issues? And then the VM crashes eventually. Best, Marcel

3 8

The Inbox: Compiler-mt.480.mcz
by commits＠source.squeak.org 20 Jul '22

20 Jul '22

A new version of Compiler was added to project The Inbox: http://source.squeak.org/inbox/Compiler-mt.480.mcz ==================== Summary ==================== Name: Compiler-mt.480 Author: mt Time: 20 July 2022, 9:49:52.740589 am UUID: 45def11a-0bef-8440-96b8-3a64f8f746b1 Ancestors: Compiler-eem.479 Alternative to Compiler-cmm.480. Let pretty-print insert line breaks in comments at 75 characters boundary. =============== Diff against Compiler-eem.479 =============== Item was changed: ----- Method: ParseNode>>printSingleComment:on:indent: (in category 'private') ----- printSingleComment: aString on: aStream indent: indent "Print the comment string, assuming it has been indented indent tabs. Break the string at word breaks, given the widths in the default + font, at 75 characters per line on average. For a mono-spaced default font, this + upper bound is exact. See TextStyle >> #defaultFont." - font, at 450 points." + (aString asText withNoLineLongerThan: 75) asString + linesDo: [:line | aStream nextPutAll: line; crtab: indent]. + aStream skip: -1 + indent negated. "Remove trailing line break."! - | readStream word position lineBreak font wordWidth tabWidth spaceWidth lastChar | - readStream := ReadStream on: aString. - font := TextStyle default defaultFont. - tabWidth := TextStyle default tabWidth. - spaceWidth := font widthOf: Character space. - position := indent * tabWidth. - lineBreak := 450. - [readStream atEnd] - whileFalse: - [word := self nextWordFrom: readStream setCharacter: [:lc | lastChar := lc]. - wordWidth := word inject: 0 into: [:width :char | width + (font widthOf: char)]. - position := position + wordWidth. - position > lineBreak - ifTrue: - [aStream skip: -1; crtab: indent. - position := indent * tabWidth + wordWidth + spaceWidth. - lastChar = Character cr - ifTrue: [[readStream peekFor: Character tab] whileTrue]. - word isEmpty ifFalse: [aStream nextPutAll: word; space]] - ifFalse: - [aStream nextPutAll: word. - readStream atEnd - ifFalse: - [position := position + spaceWidth. - aStream space]. - lastChar = Character cr - ifTrue: - [aStream skip: -1; crtab: indent. - position := indent * tabWidth. - [readStream peekFor: Character tab] whileTrue]]]!

1 0

OSProcess forkSqueak etc cause crash, 5.3 (with recent ARMv8 VM) and 6.0
by tim Rowledge 19 Jul '22

19 Jul '22

I just tried using the #forkSqueak and related methods on both my old working 5.3 image (with a recent VM) and the release 6.0 system. In both it simply blows away the system. I know it used to work but no way can I remember how long it might be since I last checked. Anybody else using a Pi (or an Apple M1/2) seeing similar? I can provide crash.dmp etc later. tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Strange OpCodes: DPN: Double Precision No-op

3 9

Call for Papers: PAINT-22 (Programming Abstractions and Interactive Notations, Tools, and Environments 2022)
by Tom Beckmann 19 Jul '22

19 Jul '22

Programming Abstractions and Interactive Notations, Tools, and Environments 2022 (PAINT-22) Co-located with SPLASH 2022 (Mon 5 - Sat 10 December 2022 Auckland, New Zealand) https://2022.splashcon.org/home/paint-2022#Call-for-Papers Call for Papers and Demos (Submissions: Thu 1 Sep 2022) -=-=-=-=-=-=-=-=-=-= *** Introduction *** Programming environments that integrate tools, notations, and abstractions into a holistic user experience can provide programmers with better support for what they want to achieve. These programming environments can create an engaging place to do new forms of informational work - resulting in enjoyable, creative, and productive experiences with programming. *** Topics of Interest *** In the workshop on Programming Abstractions and Interactive Notations, Tools, and Environments (PAINT), we want to discuss programming environments that support users in working with and creating notations and abstractions that matter to them. We are interested in the relationship between people centric notations and general-purpose programming languages and environments. How do we reflect the various experiences, needs, and priorities of the many people involved in programming — whether they call it that or not? Areas of interest to PAINT include but are not limited to: * Design and implementation of program representations and their means of interaction for end-users of all ages * Design and implementation of visual programming environments * Block-based environments and their application * Projectional editors and their application * Languages and their environments with mixed notations * Meta tools or tool creation frameworks * Methods to support working with abstractions, such as example-based programming * Input and output devices for interacting with programming environments * Theories of the above *** Important Dates *** * Submissions: Thu 1 Sep 2022 * Notifications: Sun 2 Oct 2022 * Camera-ready: Mon 24 Oct 2022 * Workshop: during SPLASH 2022 (Mon 5 - Sat 10 December 2022), to be determined *** Format *** The actual format of PAINT will depend on it being held hybrid or online. ___Remote participation will be ensured.___ We plan to organize the workshop as a one-day workshop (or up to two days with shorter slots if online) as a combination of short presentations and demos combined with structured feedback inspired by the Writer’s Workshop format: * Participants are expected to have visited the materials beforehand. * A moderator leads and directs the discussion. * We review the pieces and their ideas one at a time. * In general, the authors whose work is under review are silent. * When discussing form, the following kinds of questions will be asked: - What did you gather / understand from the piece? - What aspects of the piece worked well to present the ideas? - What aspects need improvement? (These comments must be in the form of suggestions, not criticisms.) * When discussing the ideas, the following kinds of questions will be asked: - What are the ideas? - Which ideas seem like good ones (and why)? - Which ideas need improvement or elimination? (Make positive suggestions when you can.) * At the end the authors ask questions of the group. This is the basic format, but we adjust the flow according to the needs of the group and the way the discussion is going. It is formal to ensure all the important points are covered. For more information about the workshop format, please have a look at Richard P. Gabriel’s book “Writers’ Workshops & the World of Making Things” (http://dreamsongs.com/Files/WritersWorkshopTypeset.pdf). *** Types of Submissions *** PAINT welcomes two types of contributions: * Research papers should present new, previously unpublished research in one or more of the topics described above. Six to eight pages might be considered a good target for the contributions expected at PAINT. However, there is no page limit on submitted papers. As a general rule, the number of pages should match the size of the contribution. It is the responsibility of the authors to keep the reviewers interested and motivated to read the paper. Reviewers are under no obligation to read all or even a substantial portion of a paper if they do not find the initial part of it interesting. * Demos show early implementations of novel and compelling tools, techniques, devices, and systems. Submissions should be in the form of a video no longer than 5 minutes that participants can watch prior to the workshop and then discuss. Papers and demos are to be submitted via EasyChair ( https://easychair.org/conferences/?conf=paint22). *** Publication *** Accepted papers will be published in the ACM Digital Library. (To be confirmed: Proceedings will be post-workshop to give authors the opportunity to incorporate feedback obtained at the workshop.)

1 0

The Inbox: MorphicTests-pre.88.mcz
by commits＠source.squeak.org 19 Jul '22

19 Jul '22

A new version of MorphicTests was added to project The Inbox: http://source.squeak.org/inbox/MorphicTests-pre.88.mcz ==================== Summary ==================== Name: MorphicTests-pre.88 Author: pre Time: 19 July 2022, 4:33:48.196163 pm UUID: 0260d7ea-7bc6-1443-a2a0-4092a7aaebd2 Ancestors: MorphicTests-mt.87 A morphic test case that demonstrates a) that invalid Text instances can be constructed by adding more attributes than characters b) that there can be situations when TextMorph can not handle these objects (in particular when it tries to restore the editor selection when the TextMorph gets new content). =============== Diff against MorphicTests-mt.87 =============== Item was added: + ----- Method: TextMorphTest>>testHandlingInvalidTextObjects (in category 'tests') ----- + testHandlingInvalidTextObjects + "It is possible to construct Text objects that have more attributes than characters. + This can break the TextMorph when it tries to restore the text selection." + | textMorph emptyMethodText newEmptyMethodText | + textMorph := TextMorph new. + emptyMethodText := 'emptyMethod + ' asText. + textMorph newContents: emptyMethodText. + textMorph selectFrom: 13 to: 12. + self assert: textMorph selectionInterval start = 13. + newEmptyMethodText := 'emptyMethod + ' asText. + newEmptyMethodText addAttribute: TextColor red from: 2 to: 13. + textMorph newContents: newEmptyMethodText.!

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
23
Older →

Jump to page: