Squeak-dev August 2013

squeak-dev@lists.squeakfoundation.org

45 participants
157 discussions

The Trunk: Files-eem.129.mcz
by commits＠source.squeak.org 03 Aug '13

03 Aug '13

Eliot Miranda uploaded a new version of Files to project The Trunk: http://source.squeak.org/trunk/Files-eem.129.mcz ==================== Summary ==================== Name: Files-eem.129 Author: eem Time: 2 August 2013, 4:00:55.7 pm UUID: b4aba2ed-35ae-4241-a524-2be233193f35 Ancestors: Files-fbs.128 Avoid enumerating all a directory's entries for fileExists: & directoryExists:. V important for performance. =============== Diff against Files-fbs.128 =============== Item was changed: ----- Method: FileDirectory>>directoryEntryFor: (in category 'enumeration') ----- directoryEntryFor: filenameOrPath "Answer the directory entry for the given file or path. Sorta like a poor man's stat()." | fName dir | + DirectoryClass + splitName: filenameOrPath + to: [:filePath :name | + fName := name. + dir := filePath isEmpty + ifTrue: [self] + ifFalse: [FileDirectory on: filePath]]. + + ^dir exists ifTrue: [dir directoryEntryForName: fName]! - DirectoryClass splitName: filenameOrPath to:[:filePath :name | - fName := name. - filePath isEmpty - ifTrue: [dir := self] - ifFalse: [dir := FileDirectory on: filePath]]. - self isCaseSensitive - ifTrue:[^dir entries detect:[:entry| entry name = fName] ifNone:[nil]] - ifFalse:[^dir entries detect:[:entry| entry name sameAs: fName] ifNone:[nil]]! Item was changed: ----- Method: FileDirectory>>directoryExists: (in category 'testing') ----- directoryExists: filenameOrPath "Answer true if a directory of the given name exists. The given name may be either a full path name or a local directory within this directory." "FileDirectory default directoryExists: FileDirectory default pathName" | fName dir | DirectoryClass splitName: filenameOrPath to: [:filePath :name | fName := name. dir := filePath isEmpty ifTrue: [self] + ifFalse: [FileDirectory on: filePath]]. - ifFalse: [self directoryNamed: filePath]]. ^dir exists + and: [(dir directoryEntryForName: fName) + ifNotNil: [:e| e isDirectory] + ifNil: [false]]! - and: [self class currentDirectoryNickname = fName - or: [self class parentDirectoryNickname = fName - or: [self isCaseSensitive - ifTrue:[dir directoryNames includes: fName] - ifFalse:[dir directoryNames anySatisfy: [:name| name sameAs: fName]]]]]! Item was changed: ----- Method: FileDirectory>>entryAt:ifAbsent: (in category 'file status') ----- entryAt: fileName ifAbsent: aBlock "Find the entry with local name fileName and answer it. + If not found, answer the result of evaluating aBlock." + + self exists ifFalse: [^aBlock value]. + + ^(self directoryEntryForName: fileName) ifNil: [ aBlock value ] + ! - If not found, answer the result of evaluating aBlock." - | comparisonBlock | - self isCaseSensitive - ifTrue: [comparisonBlock := [:entry | entry name = fileName]] - ifFalse: [comparisonBlock := [:entry | entry name sameAs: fileName]]. - ^ self entries detect: comparisonBlock ifNone: aBlock! Item was changed: ----- Method: FileDirectory>>fileExists: (in category 'testing') ----- fileExists: filenameOrPath "Answer true if a file of the given name exists. The given name may be either a full path name or a local file within this directory." "FileDirectory default fileExists: Smalltalk sourcesName" | fName dir | + DirectoryClass + splitName: filenameOrPath + to: [:filePath :name | - DirectoryClass splitName: filenameOrPath to: - [:filePath :name | fName := name. + dir := filePath isEmpty + ifTrue: [self] + ifFalse: [FileDirectory on: filePath]]. + + ^(dir directoryEntryForName: fName) + ifNotNil: [:e| e isDirectory not] + ifNil: [false] + ! - filePath isEmpty - ifTrue: [dir := self] - ifFalse: [dir := FileDirectory on: filePath]]. - self isCaseSensitive - ifTrue:[^dir fileNames includes: fName] - ifFalse:[^dir fileNames anySatisfy: [:name| name sameAs: fName]]. !

1 0

New Cog VMs available
by Eliot Miranda 03 Aug '13

03 Aug '13

...at http://www.mirandabanda.org/files/Cog/VM/VM.r2761/. CogVM binaries as per VMMaker.oscog-eem.317/r2761 Fix bug in transferTo:(from:) when doing a code compaction when ensuring there is a machine code method when switching to a process whose context has a machine code pc. Limit the ammount of space the Cogit will stack allocate when compiling. This limits the maximum number of bytecodes in a method that the Cogit will compile. Currently set at 1.5Mb of stack space from empirical tests of alloca on Mac OS X 10.6, linux 2.6 & Windows XP. Fix become for cog methods that are not paired with their bytecoded methods (e.g. Newspeak accessors). Linux: There are two variants of the Linux VMs; those ending in "ht" have a heartbeat thread, while those that don't, use an interval timer for the heartbeat (the Windows and Mac VMs have a threaded heartbeat). The threaded heartbeat is better (for example, signals from the interval timer interfere with system calls, etc), but to use it one must have a kernel later than 2.6.12 and configure linux to allow the VM to use multiple thread priorities. To do so, create a file called VM.conf where VM is the name of the vm executable ("squeak" for the Squeak vm, "nsvm" for the Newspeak vm) in /etc/security/limits.d/ with contents: * hard rtprio 2 * soft rtprio 2 e.g. sudo cat >/etc/security/limits.d/squeak.conf <<END * hard rtprio 2 * soft rtprio 2 sudo cp /etc/security/limits.d/squeak.conf /etc/security/limits.d/nsvm.conf END Then log out and log back in for the limits to take effect. -- best, Eliot

3 3

Stripping vs. Assembling
by Chris Muller 02 Aug '13

02 Aug '13

Hi Frank, > Yes, but the stripping out part is manual. Well, it's scripted [1], > and when a new package becomes unloadable I add it to the script, run > ... snip ... I was thinking about something. Your Stripping script, and any external ".st" script for that matter, should be a one-liner simply to call one single method, rather than having any sort of code with implementation details. One reason for this is so that browsing senders will miss as little as possible due to being externalized in an .st script. But another reason is because Stripping should be regarded *as valuable* a use-case as Assembling. There are two scenarios for deploying a minimal production image. The "conventional" way, used by other languages, is to develop the code base in a rich fat image and, when its ready, version it all up and Assemble it manually into a brand new SqueakTrunk image, sans all the richness. The other way, supported only by Smalltalk, is where I start with a ReleaseSqueakTrunk image (rich and fat) and develop my code and objects until I'm ready to deploy. Instead of being required to hand-assemble a new image I simply Strip the image I'm in and deploy that. (As I type this e-mail, the merits of Spoons approach continue to woo me. Craig?!)

4 6

HasNewFinalization important?
by Bob Arning 02 Aug '13

02 Aug '13

WeakFinalizationList instanceVariableNames: 'first' classVariableNames: 'HasNewFinalization ... I've been trying to figure out why some code of mine is failing. WeakRegistries are in the mix and I notice that HasNewFinalization is false. Does this matter? Cheers, Bob

3 2

Squeak runtime for MacOS 10.7.5
by Trygve Reenskaug 01 Aug '13

01 Aug '13

Hi all I run Smalltalk on WIN-XP SP3. My Smalltalk version answers 'Squeak3.10.2 but I may actually be running Squeak VM-3.10.6 Can anyone please point me to a Squeak runtime for *MacOS 10.7.5* that can run my DCI image that is derived from the *Squeak3.10.1-7179-basic*.image?. I'll be very grateful for any help --Trygve -- Trygve Reenskaug mailto: trygver(a)ifi.uio.no Morgedalsvn. 5A http://folk.uio.no/trygver/ N-0378 Oslo http://fullOO.info Norway Tel: (+47) 22 49 57 27

3 2

Re: [squeak-dev] Stripping vs. Assembling
by Frank Shearar 01 Aug '13

01 Aug '13

On 1 August 2013 14:45, Jecel Assumpcao Jr. <jecel(a)merlintec.com> wrote: > Frank Shearar wrote: > >> I'm prepared to be argued over to agreeing with you, which means that >> at the moment I don't :). The reason is that I don't see a car factory >> inside my car: the car factory assembles a bunch of bits and gives me >> a car. (This is one of the things that annoys me about Metacello: I >> don't want to see ConfigurationOfs in my image.) > > But there is a bacteria factory inside a bacteria :-) > > That doesn't mean that I don't prefer Smalltalks that grow (like > Smalltalk Express, a.k.a. Smalltalk V/Win) to those you have to strip. > >> Stripping is _hard_. Just look at all the Self literature. (My brief >> Googling has failed me, but I did read an interesting approach in >> connection with abstract interpretation.) Well. It's very easy to >> remove things from an image. The problem is removing only the bad bits >> and leaving the good bits. > > The automatic approach was based on type inference rather than abstract > interpretation: > > http://selflanguage.org/documentation/published/gold.html > "Sifting Out the Gold: Delivering Compact Applications From an > Exploratory Object-Oriented Environment" > Ole Agesen and David Ungar Yes! That's the one! frank > There is also David Ungar's work on the Transporter where users have to > manually annotate objects so they can be moved between images. This can > be combined with the fact that the Self VM can start with a very minimal > "empty world" and bootstrap from a bunch of text files (the text to > bytecodes compiler is in the VM instead of the image) to deliver a > stripped down system with just the application. But I think that the > automatic solution in the above paper is more interesting for this > discussion. > > -- Jecel > >

1 1

Morph layout madness
by tim Rowledge 01 Aug '13

01 Aug '13

Here's a fun way to kill a few braincells. I've been tearing much hair out for the last couple of days trying to work this one out; why do my morphs not go where they ought? Consider a morph with a submorph AlignmentMorph (I know, you don't need to use AlignmentMorphs so much now) that in turn contains two morphs. Set the alignmenmorph's right to the main morphs right-10. Open it; what do you expect? I'd expect to find the pair of morphs lined up near the main morphs right side. Nah. Don't be silly. Try out this code - |m am| m := Morph new color: Color white; extent: 200@100. am := AlignmentMorph newRow hResizing: #shrinkWrap; vResizing: #shrinkWrap; listDirection: #leftToRight; color: Color transparent. am addMorph: (Morph new color: Color red; extent: 37@51). am addMorph: (Morph new color: Color blue; extent: 43@51). m addMorph: am. am right: m right -10. am top: m top +2. m openInWorld Now change the listDirection: #leftToRight; to listDirection: #rightToLeft and see what happens. I think that is just plain wrong. Better yet, add 'am right: m right -10.' after the openInWorld. Now it goes where you expect. So, what is changing things, why, is it a bug that can be fixed, what the hell? tim -- tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful random insult:- His shared libraries aren't installed.

2 3

Jump to page: