Squeak-dev August 2001

squeak-dev@lists.squeakfoundation.org

187 participants
488 discussions

[newbie] Debugging Question.
by Philip Knodle 30 Aug '01

30 Aug '01

I'm relatively new to both Smalltalk and Squeak. I'm wondering how I can debug my code. How do I insert breakpoints in my code. Also is there a Read-Eval-Print loop similar to the ones in LISP? I've used the Workspaces, but I would prefer something closer to a REPL when debugging. Thank you, Philip Knodle -- Halley's Comet: It came, we saw, we drank.

2 1

Re: Crash on Semaphore wait
by Leandro Caniglia 30 Aug '01

30 Aug '01

Im in Linux too (4173) and cannot see any problem with Semaphore new wait + halt. May be my VM is note the same as yours. Mine is Squeak3.1alpha of 7 March 2001 [latest update: #4026] /Leandro Luciano Notarfrancesco <core.lists.squeak(a)core-sdi.com> wrote: > Semaphore new wait <alt><d> > > now try to halt with <alt><.> > > In my fully updated image running on a linux VM compiled from > Squeak-3.1a-4164pre1-src.tar.gz, it crashes. I get this from the VM: > scheduler could not find a runnable process > > 1091496604 Semaphore>waitTimeoutMSecs: > 1091354480 EventSensor>ioProcess > 1091354696 [] in EventSensor>startUp > 1091354788 [] in BlockContext>newProcess > > Any idea? > > Luciano.- > > --- for a personal reply use: Luciano Notarfrancesco <luciano(a)corest.com>

1 0

[BUG?] Image doesn't ask for initials?
by Henrik Gedenryd 30 Aug '01

30 Aug '01

It appears that Squeak-3.1a doesn't always ask for initials nowadays. I get a lot of code with "squeak" as the changer's initials when I work. I'm sorry I can't diagnose this any better now, but it may have to do with detecting that the image has moved. Has anything changed in the flie system code? Henrik

1 0

[biosqueak] First pass at a welcome page
by Bruce Oneel 30 Aug '01

30 Aug '01

is here. http://www.mysunrise.ch/users/beoneel/bioSqueak/ suggestions? cheers bruce

1 0

new book for Algorithm or Calendar Nuts
by David N. Smith (IBM) 30 Aug '01

30 Aug '01

If you're really interested in calendars, the long awaited second edition of Calendrical Calculations is now out. It's 420+ pages with everything you ever wanted to know about calendars and a whole lot more. It's by Reingold and Dershowitz, Cambridge University Press, soft cover ISBN is 0-521-77752-6. This edition includes a CD with the code for the calendars in Java, LISP, and Mathematica. (I have no connection, blah, blah, ...) Dave

1 0

RE: SWT 0.6 + Squeak VM 3.1 Alpha1 : <primitive: 141> ^ self pri mitiveFailed
by Torsten.Bergmann＠phaidros.com 30 Aug '01

30 Aug '01

Thanks - the Module Manager und Module Browser show the correct contents with that. Torsten -----Original Message----- From: Andres Valloud [mailto:sqrmax@prodigy.net] Sent: Donnerstag, 30. August 2001 17:36 To: squeak-dev(a)lists.squeakfoundation.org Subject: Re: SWT 0.6 + Squeak VM 3.1 Alpha1 : <primitive: 141> ^ self primitiveFailed Hi. > Apparently, primitive 141 only takes strings and for some reason it's > being passed aSymbol. Changing the sender to make sure aString is being > sent with the message fixes this problem. And here's the new TowardsNextRelease module (decompress attachment inside SqueakBase). You may load it with url := (RepositoryUrl fromString: 'repos://SqueakBase/TowardsNextRelease/0.1'). Andres.

1 0

[ENH]WorldTimeMorph
by Karl Ramberg 30 Aug '01

30 Aug '01

Do you ever wonder what time it is in Australia when you are in Sweden. Here is a primitive solution to that problem. File in this change set. It will download a image of the world, display it as a morph with vertical lines approximately at every time zone and the hour at each zone. The times will probably show up wrong, I did not find general way for Squeak to tell which zone I live in so I hardcoded a instance variable. Solution: -Look at the morph, locate your approximate location in the relating to the map. Count the number of vertical lines to where you are (from left). -inspect the morph -write: self localTimeSone: "<-insert the number of lines here". self changed. -select the text and doIt. Enjoy, Karl

7 17

Re: Essen ESUG experience report day 2
by joseph pelrine 30 Aug '01

30 Aug '01

I'd like to sincerely thank John McIntosh for his write-up of my talk. I hope it will serve to eliminate some of the FUD surrounding my/our work. I'll try to post some additions and comments to his article in the next few days. Sometimes the simplest ideas are the hardest to understand;-) I was also very happy after talking to Hans-Martin, where we realized that all his wishes and plans (layering modules, rollback to previous versions of methods etc.) could be very easily implemented within the ModSqueak "framework". The code for the June 29 ModSqueak code drop (the latest version that Paul and I worked on) has been available on the Stable Squeak swiki at http://swiki.squeakfoundation.org/stablesqueak. I will start describing/documenting it there. If people are interested AND if I have time, I could probably post the code for the remote installation demo too. Let me know if you want it. cheers - Joseph At 02:17 30.08.2001 , Les Tyrrell wrote: > I loved the stuff about ModSqueak, but where can I get it? Don't tell me to > download SWT 0.6- I've already checked, and it appears that ModSqueak is not in that. - les -- Joseph Pelrine

3 2

Crash on Semaphore wait
by Luciano Notarfrancesco 30 Aug '01

30 Aug '01

Semaphore new wait <alt><d> now try to halt with <alt><.> In my fully updated image running on a linux VM compiled from Squeak-3.1a-4164pre1-src.tar.gz, it crashes. I get this from the VM: scheduler could not find a runnable process 1091496604 Semaphore>waitTimeoutMSecs: 1091354480 EventSensor>ioProcess 1091354696 [] in EventSensor>startUp 1091354788 [] in BlockContext>newProcess Any idea? Luciano.- --- for a personal reply use: Luciano Notarfrancesco <luciano(a)corest.com>

1 0

[Modules] Components and Packages
by Anthony Hannan 30 Aug '01

30 Aug '01

Components: I picture a Component as an independent system that I can send messages to. Each message may cause changes in the data I refer to in the message, cause changes in the component itself, cause messages to be sent to other components, and/or cause result data to be returned. Data (message arguments and results) are trees of data records, aka, objects but without predefined behavior. Receiving components define their own behavior for each type (class) of record. If a component sees a class it does not know about it raises an error. Eliminating behavior from message arguments/results decouples components, allowing them to be changed independently. They only have to agree on record format and class identity. But unlike traditional stationary systems, components can expand and migrate across machines as necessary (like a blob). If two components reside in the same Squeak image then sending messages between them just involves pasing object pointers (like normal object sends). But if they reside on different machines then sending messages involves encoding the objects into an image segment stream, sending it, and then decoding it on the other side. Furthermore, to maintain object identity only remote references of objects can be passed, however, free (about to be garbage collected) and immutable objects can be passed as whole objects. When a component wants to execute a method on a remote object it received from a remote machine, it loads a copy of itself on the remote machine and executes its method there, where the object resides. Changes to component globals/behaviors are kept in synch across machines. Packages: If the remote machine already contains some of the behavior that is needed by the migrating component, it would be nice if it could reuse that behavior, without loading a redundant copy. This is where packages come in. A Component is an environment that inherits from one or more immutable packages. A Package is a set of immutable globals, behaviors, and inherited packages. Packages are layered, so a package may override a global/behavior defined in one of its inherited packages. A package has a single name space that includes all the names of its inherited packages. Ambiguities in inherited names are explicitly resolved by overriding the effected objects with new names. So when loading a component, the Squeak image only needs to load packages that are not already loaded (for other components). A component is really just a mutable package, it has its own globals/behavior that add to or override the packages it inherits from. A component has a single name space, but because it can reference other components and get objects from thm by sending messages to them, you basically have nested name spaces as well. Conclusion: In today's Internet world, we need a modular solution that directly addresses distributed Squeak systems as well as the traditional building of custom local systems. The current Project class stuff could work well in a distributed component architecture like the one described here. Components are isolated and are quickly migratable if immutable incremental packages are used. Inheriting fixed immutable packages are preferred to inheriting a range of versions or inheriting a changeable package because otherwise a single distributed component could behave differently depending on what machine its executing on. Changes to a components behavior would involve creating a new incremental package that inherits from the old packages and then updating the component to inherit from the new package. This change would automatically be propogated to other machines where the component is loaded, causing the new package to be distibuted to the other machines automatically. And since components are isolated, it would not affect other work. Objects are easily convertable to components and vise versa. If an object and related objects do a lot of work that is pretty well separate from the rest of the system, and sends relatively few messages to arguments coming in on messages sent to it, then the object is a good candidate for becoming its own component. Senders would not have to change at all. You just have to make the object a subclass of Component, and then make sure it inherits from the package(s) that defines the messages you send to arguments and other objects your component points to. Some analysis tool could help with this. I hope this make sense to some (hopefully most) of you. Cheers, Anthony

14 22

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

Jump to page: