Squeak-dev February 2011

squeak-dev@lists.squeakfoundation.org

87 participants
295 discussions

[ANN] Squeak 4.2
by Chris Muller 22 Feb '11

22 Feb '11

I'd like to call Squeak 4.2 finally officially released now. I posted the first maintenance "fix" to the squeak42 repository the other day, so our process for applying maintenance updates has been tested, in case we should need any more. I'm still waiting for final web-site updates from Janko, but I see no reason to postpone announcing any longer. Thanks so much to Levente, Igor, Andreas and many others who contributed. Our development process seems to be working, and that deserves credit for us having ended up with a pretty good release this time. It will be nice to have 4.2 behind us in terms of future development. Cheers! Chris

9 14

Re: What was the idea behind the colorful windows?
by Dan Ingalls 22 Feb '11

22 Feb '11

Hi Bert, and all - Yes, the rationale behind different colors had to do with different functions in a busy screen, especially useful for partially obscured or collapsed windows. I found this important as a developer, but I never dreamed of inflicting the panoply on end-users. With regard to the choice of colors, I did not attach any great significance to it except the obvious red for errors and, by association, the debugger. In choosing green for the browser I think I was thinking of the pale green used for some graph paper; I didn't want anything too contrasty (after having tried that for a while). And the workspace color was an allusion to parchment for useful notes; I recall the first post-its being yellow too. The shades are not the best (someone once mentioned Necco Wafers). I know they replulse some people, but they have always been changeable. All that nice ability to change "themes" was put in by other people. I can only take credit for making things bad enough that the community came forth with the necessary improvements ;-). - Dan -------------------------------------- >Hi Dan, > >were the colors just random, or do you remember picking e.g. the browser's green consciously? > >- Bert - > >Begin forwarded message: > >> From: Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> >> Date: 20. Februar 2011 23:53:56 GMT-08:00 > > To: squeak-dev(a)lists.squeakfoundation.org >> Subject: [squeak-dev] Re: What was the idea behind the colorful windows? >> Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> >> >>> >>>> i heard in some esug video that there had beed an idea and a system behind >>>> the colorful windows. Is there some place where i can find information >>>> about >>>> it? >>> >>> Not sure if it was an idea behind it but one obvious advantage of having >>> different kinds of tools use different colors is that it makes it much >>> easier finding them when you have a whole stack of overlapping windows >>> to dig around in - (which btw is a very common Smalltalk "disease" since >>> we have too many shortcuts that spawn new windows). For example, >>> something pink sticking out there? Aha, a debugger. >>> >> yes, of course. i meant to ask, if certain colors do have specific meanings? >> -- >> View this message in context: http://forum.world.st/What-was-the-idea-behind-the-colorful-windows-tp33153… >> Sent from the Squeak - Dev mailing list archive at Nabble.com. >>

1 0

Daily Commit Log
by commits＠source.squeak.org 22 Feb '11

22 Feb '11

Changes to Trunk (http://source.squeak.org/trunk.html) in the last 24 hours: http://lists.squeakfoundation.org/pipermail/packages/2011-February/004301.h… Name: Morphic-mtf.521 Ancestors: Morphic-nice.520 created HandMorph >> dragThreshold to hold the default drag threshold Changed drag users to use this setting rather than make up their own thresholds Finished a partial change of SystemWindow from simulating its own dragging to using the builtin drag mechanism Made the default drag threshold zero pixels. it was previously 0, 5, or 10 pixels, depending on the morph ============================================= http://lists.squeakfoundation.org/pipermail/packages/2011-February/004302.h… Name: SystemReporter-laza.18 Ancestors: SystemReporter-laza.17 Show /proc/version in the LinuxOSDetails report =============================================

1 0

The Trunk: SystemReporter-laza.18.mcz
by commits＠source.squeak.org 22 Feb '11

22 Feb '11

Alexander Lazarević uploaded a new version of SystemReporter to project The Trunk: http://source.squeak.org/trunk/SystemReporter-laza.18.mcz ==================== Summary ==================== Name: SystemReporter-laza.18 Author: laza Time: 22 February 2011, 12:06:28.268 am UUID: 68ae866a-6780-4e2b-b4b4-d2c1cfcd4b01 Ancestors: SystemReporter-laza.17 Show /proc/version in the LinuxOSDetails report =============== Diff against SystemReporter-laza.17 =============== Item was changed: ----- Method: SystemReporter>>reportLinuxOSDetails: (in category 'reporting') ----- reportLinuxOSDetails: aStream self header: 'Operating System Details' on: aStream. #( '/etc/issue' '/etc/lsb-release' + '/proc/version' - "'/proc/version'" "Squeak can't read this?!!" ) do: [:path| self writeContentsSafelyFromFile: path on: aStream]! Item was changed: ----- Method: SystemReporter>>writeContentsSafelyFromFile:on: (in category 'private') ----- writeContentsSafelyFromFile: osPath on: aStream aStream nextPutAll: ([ + (FileStream readOnlyFileNamed: osPath) upToEnd - (FileStream readOnlyFileNamed: osPath) contentsOfEntireFile ] on: Error do: [:ex| ex return: ex printString])!

1 0

Linux VM can't read files from /proc
by Alexander Lazarević 21 Feb '11

21 Feb '11

Does anybody know why the linux vm can't read files from the /proc filesystem? The VM is able to open the files but the size is 0!? A simple less or cat on these files just works fine ... Alex

2 1

The Trunk: Morphic-mtf.521.mcz
by commits＠source.squeak.org 21 Feb '11

21 Feb '11

Matthew Fulmer uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-mtf.521.mcz ==================== Summary ==================== Name: Morphic-mtf.521 Author: mtf Time: 21 February 2011, 4:29:10.979 pm UUID: cf57b307-096f-4311-a02e-b1f53d206e9c Ancestors: Morphic-nice.520 created HandMorph >> dragThreshold to hold the default drag threshold Changed drag users to use this setting rather than make up their own thresholds Finished a partial change of SystemWindow from simulating its own dragging to using the builtin drag mechanism Made the default drag threshold zero pixels. it was previously 0, 5, or 10 pixels, depending on the morph =============== Diff against Morphic-nice.520 =============== Item was changed: ----- Method: ClickExerciser>>mouseDown: (in category 'event handling') ----- mouseDown: evt "Do nothing upon mouse-down except inform the hand to watch for a double-click; wait until an ensuing click:, doubleClick:, or drag: message gets dispatched" Preferences disable: #NewClickTest . evt hand waitForClicksOrDrag: self event: evt selectors: self selectors + threshold: HandMorph dragThreshold! - threshold: 10 - ! Item was changed: ----- Method: HaloMorph>>blueButtonDown: (in category 'meta-actions') ----- blueButtonDown: event "Transfer the halo to the next likely recipient" target ifNil:[^self delete]. event hand obtainHalo: self. positionOffset := event position - (target point: target position in: owner). self isMagicHalo ifTrue:[ self isMagicHalo: false. ^self magicAlpha: 1.0]. "wait for drags or transfer" event hand waitForClicksOrDrag: self event: event selectors: { #transferHalo:. nil. nil. #dragTarget:. } + threshold: HandMorph dragThreshold! - threshold: 5.! Item was changed: Morph subclass: #HandMorph instanceVariableNames: 'mouseFocus keyboardFocus eventListeners mouseListeners keyboardListeners mouseClickState mouseOverHandler lastMouseEvent targetOffset damageRecorder cacheCanvas cachedCanvasHasHoles temporaryCursor temporaryCursorOffset hardwareCursor hasChanged savedPatch userInitials lastEventBuffer genieGestureProcessor keyboardInterpreter' + classVariableNames: 'CompositionWindowManager DoubleClickTime DragThreshold EventStats NewEventRules NormalCursor PasteBuffer ShowEvents' - classVariableNames: 'CompositionWindowManager DoubleClickTime EventStats NewEventRules NormalCursor PasteBuffer ShowEvents' poolDictionaries: 'EventSensorConstants' category: 'Morphic-Kernel'! !HandMorph commentStamp: '<historical>' prior: 0! The cursor may be thought of as the HandMorph. The hand's submorphs hold anything being carried by dragging. There is some minimal support for multiple hands in the same world.! Item was added: + ----- Method: HandMorph class>>dragThreshold (in category 'accessing') ----- + dragThreshold + + ^ DragThreshold + ! Item was added: + ----- Method: HandMorph class>>dragThreshold: (in category 'accessing') ----- + dragThreshold: pixels + + DragThreshold := pixels! Item was changed: ----- Method: HandMorph class>>initialize (in category 'class initialization') ----- initialize "HandMorph initialize" PasteBuffer := nil. DoubleClickTime := 350. + DragThreshold := 0. NormalCursor := CursorWithMask normal asCursorForm. ! Item was changed: ----- Method: HandMorph>>waitForClicksOrDrag:event: (in category 'double click support') ----- waitForClicksOrDrag: aMorph event: evt "Wait for mouse button and movement events, informing aMorph about events interesting to it via callbacks. This message is typically sent to the Hand by aMorph when it first receives a mouse-down event. The callback methods invoked on aMorph (which are passed a copy of evt) are: #click: sent when the mouse button goes up within doubleClickTime. #doubleClick: sent when the mouse goes up, down, and up again all within DoubleClickTime. #doubleClickTimeout: sent when the mouse does not have a doubleClick within DoubleClickTime. #startDrag: sent when the mouse moves more than 10 pixels from evt's position within DoubleClickTime. Note that mouseMove: and mouseUp: events are not sent to aMorph until it becomes the mouse focus, which is typically done by aMorph in its click:, doubleClick:, or drag: methods." + ^self waitForClicksOrDrag: aMorph event: evt selectors: #( #click: #doubleClick: #doubleClickTimeout: #startDrag:) threshold: HandMorph dragThreshold! - ^self waitForClicksOrDrag: aMorph event: evt selectors: #( #click: #doubleClick: #doubleClickTimeout: #startDrag:) threshold: 10 - ! Item was changed: ----- Method: Morph>>blueButtonDown: (in category 'meta-actions') ----- blueButtonDown: anEvent "Special gestures (cmd-mouse on the Macintosh; Alt-mouse on Windows and Unix) allow a mouse-sensitive morph to be moved or bring up a halo for the morph." | h tfm doNotDrag | h := anEvent hand halo. "Prevent wrap around halo transfers originating from throwing the event back in" doNotDrag := false. h ifNotNil:[ (h innerTarget == self) ifTrue:[doNotDrag := true]. (h innerTarget hasOwner: self) ifTrue:[doNotDrag := true]. (self hasOwner: h target) ifTrue:[doNotDrag := true]]. tfm := (self transformedFrom: nil) inverseTransformation. "cmd-drag on flexed morphs works better this way" h := self addHalo: (anEvent transformedBy: tfm). h ifNil: [^ self]. doNotDrag ifTrue:[^self]. "Initiate drag transition if requested" anEvent hand waitForClicksOrDrag: h event: (anEvent transformedBy: tfm) selectors: { nil. nil. nil. #dragTarget:. } + threshold: HandMorph dragThreshold. - threshold: 5. "Pass focus explicitly here" anEvent hand newMouseFocus: h.! Item was changed: ----- Method: PasteUpMorph>>mouseDown: (in category 'event handling') ----- mouseDown: evt "Handle a mouse down event." | grabbedMorph handHadHalos | (Preferences generalizedYellowButtonMenu and: [evt yellowButtonPressed]) ifTrue: [^ self yellowButtonActivity: evt shiftPressed]. grabbedMorph := self morphToGrab: evt. grabbedMorph ifNotNil:[ grabbedMorph isSticky ifTrue:[^self]. self isPartsBin ifFalse:[^evt hand grabMorph: grabbedMorph]. grabbedMorph := grabbedMorph partRepresented duplicate. grabbedMorph restoreSuspendedEventHandler. (grabbedMorph fullBounds containsPoint: evt position) ifFalse:[grabbedMorph position: evt position]. "Note: grabbedMorph is ownerless after duplicate so use #grabMorph:from: instead" ^ evt hand grabMorph: grabbedMorph from: self]. (super handlesMouseDown: evt) ifTrue:[^super mouseDown: evt]. handHadHalos := evt hand halo notNil. evt hand removeHalo. "shake off halos" evt hand releaseKeyboardFocus. "shake of keyboard foci" self submorphs select:[:each | each hasProperty: #morphHierarchy] thenDo:[:each | each delete]. Preferences noviceMode ifTrue:[ self submorphs select:[:each | (each isKindOf: MenuMorph) and:[each stayUp not]] thenDo:[:each | each delete]. ]. (evt shiftPressed not and:[ self isWorldMorph not and:[ self wantsEasySelection not ]]) ifTrue:[ "explicitly ignore the event if we're not the world and we'll not select, so that we could be picked up if need be" evt wasHandled: false. ^ self. ]. ( evt shiftPressed or: [ self wantsEasySelection ] ) ifTrue:[ "We'll select on drag, let's decide what to do on click" | clickSelector | clickSelector := nil. evt shiftPressed ifTrue:[ clickSelector := #findWindow:. ] ifFalse:[ self isWorldMorph ifTrue:[ clickSelector := handHadHalos ifTrue: [ #delayedInvokeWorldMenu: ] ifFalse: [ #invokeWorldMenu: ] ] ]. evt hand waitForClicksOrDrag: self event: evt selectors: { clickSelector. nil. nil. #dragThroughOnDesktop: } + threshold: HandMorph dragThreshold. - threshold: 5. ] ifFalse:[ "We wont select, just bring world menu if I'm the world" self isWorldMorph ifTrue:[ handHadHalos ifTrue: [ self delayedInvokeWorldMenu: evt ] ifFalse: [ self invokeWorldMenu: evt ] ] ]. ! Item was changed: ----- Method: PluggableListMorph>>mouseDown: (in category 'events') ----- mouseDown: evt | selectors row | evt yellowButtonPressed "First check for option (menu) click" ifTrue: [^ self yellowButtonActivity: evt shiftPressed]. row := self rowAtLocation: evt position. row = 0 ifTrue: [^super mouseDown: evt]. "self dragEnabled ifTrue: [aMorph highlightForMouseDown]." selectors := Array with: #click: with: (doubleClickSelector ifNotNil:[#doubleClick:]) with: nil with: (self dragEnabled ifTrue:[#startDrag:] ifFalse:[nil]). + evt hand waitForClicksOrDrag: self event: evt selectors: selectors threshold: HandMorph dragThreshold "pixels".! - evt hand waitForClicksOrDrag: self event: evt selectors: selectors threshold: 10 "pixels".! Item was removed: - ----- Method: PluggableSystemWindowWithLabelButton>>mouseDown: (in category 'events') ----- - mouseDown: evt - | wasInactive | - wasInactive := TopWindow ~~ self. - self valueOfProperty: #clickPoint ifPresentDo: - [:firstClick | - (labelButton containsPoint: evt cursorPoint) ifTrue: - [^labelButton mouseDown: evt]]. - super mouseDown: evt. - (wasInactive - and: [model windowActiveOnFirstClick not - and: [labelButton containsPoint: evt cursorPoint]]) ifTrue: - [^labelButton mouseDown: evt]! Item was removed: - ----- Method: PluggableSystemWindowWithLabelButton>>passivate (in category 'top window') ----- - passivate - super passivate. - self removeProperty: #clickPoint! Item was changed: ----- Method: SimpleHierarchicalListMorph>>mouseDown: (in category 'event handling') ----- mouseDown: evt | aMorph selectors | aMorph := self itemFromPoint: evt position. (aMorph notNil and:[aMorph inToggleArea: (aMorph point: evt position from: self)]) ifTrue:[^self toggleExpandedState: aMorph event: evt]. evt yellowButtonPressed "First check for option (menu) click" ifTrue: [^ self yellowButtonActivity: evt shiftPressed]. aMorph ifNil:[^super mouseDown: evt]. aMorph highlightForMouseDown. selectors := Array with: #click: with: nil with: nil with: (self dragEnabled ifTrue:[#startDrag:] ifFalse:[nil]). + evt hand waitForClicksOrDrag: self event: evt selectors: selectors threshold: HandMorph dragThreshold "pixels".! - evt hand waitForClicksOrDrag: self event: evt selectors: selectors threshold: 10 "pixels".! Item was changed: ----- Method: SystemWindow>>handlesMouseDown: (in category 'events') ----- handlesMouseDown: evt "If I am not the topWindow, then I will only respond to dragging by the title bar. Any other click will only bring me to the top" - (self labelRect containsPoint: evt cursorPoint) - ifTrue: [^ true]. ^ self activeOnlyOnTop and: [self ~~ TopWindow]! Item was changed: ----- Method: SystemWindow>>mouseDown: (in category 'events') ----- mouseDown: evt - self setProperty: #clickPoint toValue: evt cursorPoint. TopWindow == self ifFalse: [evt hand releaseKeyboardFocus. self activate]. + + "the window was locked, thus we got the event. re-send it now that the window is unlocked again" + evt wasHandled: false. + model windowActiveOnFirstClick + ifTrue: [self processEvent: evt] "re-dispatch to any submorphs" + ifFalse: [label processEvent: evt]. "dispatch to label so dragging works" + evt wasHandled: true. - model windowActiveOnFirstClick ifTrue: - ["Normally window keeps control of first click. - Need explicit transmission for first-click activity." - submorphs do: [:m | (m containsPoint: evt cursorPoint) ifTrue: [m mouseDown: evt]]] - ! Item was removed: - ----- Method: SystemWindow>>mouseMove: (in category 'events') ----- - mouseMove: evt - "Handle a mouse-move event" - - | cp | - cp := evt cursorPoint. - self valueOfProperty: #clickPoint ifPresentDo: - [:firstClick | - ((self labelRect containsPoint: firstClick) and: [(cp dist: firstClick) > 3]) ifTrue: - ["If this is a drag that started in the title bar, then pick me up" - ^ self isSticky ifFalse: - [self fastFramingOn - ifTrue: [self doFastFrameDrag: firstClick] - ifFalse: [evt hand grabMorph: self topRendererOrSelf]]]]. - model windowActiveOnFirstClick ifTrue: - ["Normally window takes control on first click. - Need explicit transmission for first-click activity." - submorphs do: [:m | (m containsPoint: cp) ifTrue: [m mouseMove: evt]]]! Item was changed: ----- Method: SystemWindow>>startDragFromLabel: (in category 'events') ----- startDragFromLabel: evt "When label events are active, we need to pass dragging to the window explicitely The window only recognizes a drag with an offset of more than 3 pixels" + self isSticky ifTrue: [^ self]. + self fastFramingOn + ifTrue: [self doFastFrameDrag: evt cursorPoint] + ifFalse: [evt hand grabMorph: self topRendererOrSelf] + ! - self setProperty: #clickPoint toValue: evt cursorPoint - 4. - self mouseMove: evt.!

1 0

Re: [squeak-dev] add repositories to Monticello by script?
by Hernán Morales Durand 21 Feb '11

21 Feb '11

2011/2/20 Ken G. Brown <kbrown(a)mac.com>: > Is there a way to add repositories to Monticello by script so you don't have to use the +Repository button multiple times? > > Thx for any tips. > Ken G. Brown > > | repositories | repositories := MCRepositoryGroup default. { (MCHttpRepository location: 'http://www.squeaksource.com/Phantasia' user: '' password: ''). (MCHttpRepository location: 'http://www.squeaksource.com/SmallFaces' user: '' password: ''). } do: [ : aRepository | repositories addRepository: aRepository ] Hernán

2 1

SqueakSource down... again
by Hernán Morales Durand 21 Feb '11

21 Feb '11

SqueakSource is down again. I'm tired of this situation, there is any alternative "free" repository? Cheers, -- Hernán Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

1 0

Re: [Pharo-project] Cog VM -- Thanks and Performance / Optimization Questions
by Eliot Miranda 21 Feb '11

21 Feb '11

Hi John, good questions. On Thu, Feb 17, 2011 at 6:21 AM, John B Thiel <jbthiel(a)gmail.com> wrote: > Cog VM -- Thanks and Performance / Optimization Questions > > > To Everyone, thanks for your great work on Pharo and Squeak, and to > Eliot Miranda, Ian Piumarta, and all VM/JIT gurus, especially thanks > for the Squeak VM Cog and its precursors, which I was keenly > anticipating for a decade or so, and is really going into stride with > the latest builds. > > I like to code with awareness of performance issues. Can you tell or > point me to some performance and efficiency tips for Cog and the > Squeak compiler -- detail on which methods are inlined, best among > alternatives, etc. For example, I understand #to:do: is inlined -- > what about #to:do:by: and #timesRepeat and #repeat ? Basically, I > would like to read a full overview of which core methods are specially > optimized (or planned). > The bytecode compiler inlines a set of selectors if the arguments are suitable (typically literal blocks). The standard compiler's list is MessageNode classPool at: #MacroSelectors, e.g. #ifTrue: #ifFalse: #ifTrue:ifFalse: #ifFalse:ifTrue: #and: #or: #whileFalse: #whileTrue: #whileFalse #whileTrue #to:do: #to:by:do: #caseOf: #caseOf:otherwise: #ifNil: #ifNotNil: #ifNil:ifNotNil: #ifNotNil:ifNil: Note that Nicolas Cellier has just added support for inlining repeat and timesRepeat in Squeak trunk. > I know about the list of NoLookup primitives, as per Object > class>>howToModifyPrimitives, supposing that is still valid? > Not for Cog. While #== and #class are inlined all other primitives are looked up. > What do you think is a reasonable speed factor for number-crunching > Squeak code vs C ? I am seeing about 20x slower in the semi-large > scale, which surprised me a bit because I got about 10x on smaller > tests, and a simple fib: with beautiful Cog is now about 3x (wow!). > That range, 3x tiny tight loop, to 20x for general multi-class > computation, seems a bit wide -- is it about expected? > Are you saying that you have a macro benchmark that is 20 times faster in C than in Cog? Cog, while faster than the interpreter, is still a non-inlining, non-globally-optimizing system and so performance is certainly to be expected to be worse than C. But 20x sounds a little high so your benchmark could be useful. If you can post this please do. The current state of Cog is that the new code generator gives a significant speed-up but that the object model and garbage collector remain substantially the same as the Squeak interpreter. The GC is slow and badly needs replacing. The object model is both slow, especially for class access, which slows down all sends a little, and over-complex, which means that several performance-critical primitives have yet to be implemented in machine-code, especially at:put:, basicNew, basicNew:, and closure creation, all of which currently require expensive calls into C instead of using inline machine code. I would expect that improving all these could add at least another factor of 33%. I'm trying to find funding to work on these two issues ASAP. > My profiling does not reveal any hotspots, as such -- it's basically > 2, 3, 5% scattered around, so I envision this is just the general > vm/jit overhead as you scale up -- referencing distant objects, slots, > dispatch lookups, more cache misses, etc. But maybe I am generally > using some backwater loop/control methods, techniques, etc. that could > be tuned up. e.g. I seem to recall a trace at some point showing > #timesRepeat taking 10% of the time (?!). Also, I recall reading > about an anomaly with BlockClosures -- something like being rebuilt > every time thru the loop - has that been fixed? Any other gotchas to > watch for currently? > BlockClosures for non-inlined blocks are still created when mentioned. So if you do have a loop which contains a block creation, consider pulling the block out into a temp variable. > (Also, any notoriously slow subsystems? For example, Transcript > writing is glacial.) > Someone should replace the Transcript's reliance on (I think) some kind of FormMorph which moved huge numbers of bits on each write. But this is not a VM issue. It's a Smalltalk issue. Whoever did this would instantly become a hero. > The Squeak bytecode compiler looks fairly straightforward and > non-optimizing - just statement by statement translation. So it > misses e.g. chances to store and reuse, instead of pop, etc. I see > lots of redundant sequences emitted. Are those kind of things now > optimized out by Cog, or would tighter bytecode be another potential > optimization path. (Is that what the Opal project is targetting?) > There is some limited constant folding in the StackToRegisterMapingCogit. For example the pushTrue jumpFalse sequences generated in inlined and: and or: statements is eliminated. Also constant SmallInteger arithmetic is folded iff the receiver is a literal. The JIT doesn't have any type information so it can't fold var + 1 + 2, but it can and does fold 1 + 2 + var into 3 + var. Marcus Denker and I are working as I write on the infrastructure for an adaptive-optimizer/speculative-inliner that will initially operate at the bytecode level, deriving type information from the JIT's inline caches and using this to direct bytecode-to-bytecode optimization that will inline blocks, inline methods, etc. We hope eventually to target floating-point and other performance-critical code. Marcus posted a presentation I did a while back <Smalltalk Books Video Tutorials Smalltalk in Latam About Us! Contact Us Actually, I'm trying to make Ruby natural, not simple. -- Yukihiro "Matz" Matsumoto Home Talks & Presentations Eliot Miranda - Bytecode-to-bytecode adaptive optimization for Smalltalk Eliot Miranda - Bytecode-to-bytecode adaptive optimization for Smalltalk Last Updated (Sunday, 14 February 2010 20:21) | Written by Administrator | Monday, 18 August 2008 19:28 Multimedia Gallery - Talks & Presentations More ... Comments from the google video: This talk summarises two decades of work on Smalltalk and Self compilation and virtual machine technology and describes a novel attempt at an adaptive optimizer for Smalltalk that is written in Smalltalk and to a meaningful extent, portable across implementations. Smalltalk-80 and Self are fully object-oriented implicitly typed dynamic programming languages and interactive programming environments hosted above virtual machines that appear to execute stack-oriented bytecode for a pure stack machine. These systems' code and execution state are all represented by objects programmed in Smalltalk, such that the compiler, debugger, exception system and more are all implemented entirely in Smalltalk and available to the programmer for immediate incremental and interactive modification LikeDislike Community Disqus Add New Comment Optional: Login below. Post as … Showing 0 comments Sort by Subscribe by email Subscribe by RSS blog comments powered by DISQUS back to top < Prev Next > Main Menu Home ClubSmalltalk Merchandise About Us! Contact Us Articles Frontpage news Interviews Community ClubSmalltalk | Mailing List [In Spanish] ClubSmalltalk | LinkedIn Group ClubSmalltalk | Facebook ClubSmalltalk | Community Blogs Smalltalkers Blogs & Personal pages Smalltalkers - Social Network Environments Commercial Smalltalk Environments Free Smalltalk Environments Abbandon Smalltalk Environments Frameworks, Platforms & Tools FAQ Smalltalk Frequently Asked Questions GemStone Frequently Asked Questions ENVY/Manager Frequently Asked Questions Resources Smalltalk Jobs! Smalltalk Web Links Smalltalk News Feeds Smalltalk Books Smalltalk Podcasts Multimedia Gallery Back to the future - Photo Gallery Smalltalk History Channel Talks & Presentations Smalltalk Documentaries Login If you don't want to register in this site, you can use your Gmail or OpenId authentication. Username Password Remember Me Forgot your password? Forgot your username? Create an account Login with an OpenID What is OpenId? Smalltalk on Twitter J_WICKS_CTE (J.Wicks) : I hate 2 word sentences #smalltalk 11th_echo (Yvonne) : Da fand er unseren Smalltalk wohl so einlullend, dass er erstmal seine Schlüssel liegen ließ :DDDDDDDDDDDD höhö Dennis_Klinger (Dennis Klinger) : benachrichtigung bei antwort: hi leute ich hab mal ne frage. wie kann man sich benachrichtigen lassen wenn in ... http://bit.ly/gTytl0 onizee (Oneal Madumo) : Those who understnd #smalltalk ,guy walks in on me in th gym showers,and he says,"eish o tshwara shawara",how do i respond to this? JusCardo (Ricardo Cherry) : #SMALLtalk RT @_SweetTeee @JusCardo lol I hate you Paypal Donation Please, make a Paypal donation at least of 1 dollar! Thanks! Copyright © 2011 ClubSmalltalk. All Rights Reserved. Contact Us! Please, if you like the site visit our sponsors. Thanks.> that covers the essential ideas. This project could completely close the gap to C if augmented by a good quality code generator. At least, that's a goal. > -- jbthiel > >

5 7

What was the idea behind the colorful windows?
by Helene Bilbo 21 Feb '11

21 Feb '11

Hi, i heard in some esug video that there had beed an idea and a system behind the colorful windows. Is there some place where i can find information about it? (i like the colors :) best regards, Helene. -- View this message in context: http://forum.world.st/What-was-the-idea-behind-the-colorful-windows-tp33153… Sent from the Squeak - Dev mailing list archive at Nabble.com.

4 4

← Newer
1
...
6
7
8
9
10
11
12
...
30
Older →

Jump to page: