December 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Dictionary responds to #add:, #addAll: but shouldNotImplement #remove: and #remove:ifAbsent
by jaayer Dec. 8, 2010

Dec. 8, 2010

Is anyone else bother by this inconsistency?

4 12

[Pharo-project] socket deadlock using Cog VM
by Johan Brichau Dec. 8, 2010

Dec. 8, 2010

Hi, We are experiencing a deadlock in Socket>>waitForDataIfClosed: The problem occurs on Pharo11/Pharo12/Squeak41 only when using the Cog VM. In our particular case, the socket connects to a GOODS database and it started occurring with a growing amount of data (so longer connections, more data transfer). When you open a debugger on the deadlocked process and proceed the process, it will simply continue and finish without problems. We are using Cog VM of 4 october, downloaded from Eliot's website (VM.r2316/) Before I start isolating the problem and reproduce it without requiring GOODS (it's just an http socket anyway): Is anyone else experiencing similar issues here? Is there a fix in more recent versions? cheers Johan

1 0

Re: [Pharo-project] Hudson and version number
by Marcus Denker Dec. 8, 2010

Dec. 8, 2010

On Dec 8, 2010, at 8:25 AM, Luc Fabresse wrote: > Hi all, > > I was looking the results of the 1.2 build #33. > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/33/ > > Where is displayed the version number of the 1.2 used for this build? > Was it the12271? > > I always loads all updates... so it's the version that was available at the time of build. It would be nice to display the update number... if anyone has an idea how to do that? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 3

Re: [Pharo-project] Problem updating Pharo Core
by Marcus Denker Dec. 8, 2010

Dec. 8, 2010

On Dec 7, 2010, at 12:17 PM, Gary Chambers wrote: > Does the build server run Windows? (c.f. $: in package name). > No, we have right now just a Linux builder. But we will add Mac soon, after that windows. > Regards, Gary > ----- Original Message ----- > From: Marcus Denker > To: Pharo-project(a)lists.gforge.inria.fr > Sent: Monday, December 06, 2010 9:11 PM > Subject: Re: [Pharo-project] Problem updating Pharo Core > > > On Dec 6, 2010, at 7:59 PM, Guillermo Polito wrote: > >> I have the last prebuild pharo core (12261), and clicking on update stops in version 12266 with a DNU: >> >> nil does not understand binary >> >> It has something to do with the monticello a version with this info: 'Issue 3191: SparseLargeArray-MarcusDenker.2.mcz' >> >> Did someone had this same issue? >> > > the build server seems to have no problem: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/ > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Hudson and version number
by Luc Fabresse Dec. 8, 2010

Dec. 8, 2010

Hi all, I was looking the results of the 1.2 build #33. https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/33/ Where is displayed the version number of the 1.2 used for this build? Was it the12271? Thanks, #Luc

1 0

[Pharo-project] Pharo integration in enterprise feedback
by laurent laffont Dec. 8, 2010

Dec. 8, 2010

Hi, I'm looking for feedback on Pharo integration in enterprise. Especially how you have managed to put Pharo in your enterprise. For example, I'm involved in web application development in other languages. For functional testing I'm able to script Selenium using Pharo thanks to WebTester. So Pharo has made a small step at my work. I'm looking for such stories. Cheers, Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

11 25

[Pharo-project] Smalltalk in small steps ?
by James Ladd Dec. 7, 2010

Dec. 7, 2010

Hi All, As some of you may know I am writing a Smalltalk for the Java Virtual Machine and it is coming along well. http://redline.st with source on http://github.com Recently I came across a series of blog posts by Peter Michaux on Scheme from scratch and I wondered: Would it be worth while for the Smalltalk community, and language enthusiasts if I were to do the same with Redline Smalltalk, that is, make each features implementation part of a blog post and a 'work along' ? Would you like to see this and or work along with Redline ? Rgs, James.

6 5

[Pharo-project] ProcessWrapper
by Facundo Vozzi Dec. 7, 2010

Dec. 7, 2010

Hi all, anybody is using ProcessWrapper in Pharo 1.1.1 ? I'm using windows and It works fine on Squeak 4.1.1 but it doesn't on my Pharo 1.1.1 which is my development environment. Thanks in advance, Facu

3 5

[Pharo-project] IRC meeting notes
by Adrian Lienhard Dec. 7, 2010

Dec. 7, 2010

This evening the announced IRC meeting took place. I've published the notes as a blog post on our website: http://pharo-project.org/news?article=irc-meeting-notes Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

2 1

[Pharo-project] 'stash' a Smalltalk shell or what happens when you let your mind wander in the shower....
by Dale Henrichs Dec. 7, 2010

Dec. 7, 2010

I was thinking about a number of things in the shower this morning and then it occurred to me that it would be interesting to create a shell environment INSIDE a Smalltalk vm. It wouldn't be a complete environment, but it would include a small set of standard unix utilities: - awk - sed - grep the "directory structure" would be the package structure in the image (or maybe multiple views on the image contents) with the basic idea that you 'cd' into a class where there is a 'file' that contains the class attributes. you then 'cd instance/all' and you are in a "directory" of methods where you can 'vi at:put:' and have a vi-like editor come up on the source of the at:put: method of course awk, grep, and sed work on all of these 'source files'... there would be 'executable files' that are simply workspaces ... I know that folks have externalized files, but I don't know if anyone has internalized the shell environment ... The reason for internalizing the shell is that it becomes easy to transition to the debugger and other traditional browsers/windows. The big reason for internalizing the shell is to provide a unix-like interface for Smalltalk that might make transition to the Smalltalk tools easier for folks new to Smalltalk. The secondary reason (and probably just as important) for internalizing the shell, is that the hard-core Smalltalk developers might actually find some utility in using the "smalltalk shell" in the normal course of development and if hard-core developers use it, it will be maintained and might lead to other interesting things... The idea is that the entire "smalltalk shell" would be implemented in Smalltalk so you could bring up browsers with a command ... I've been thinking wistfully back to the days when I lived inside of Emacs in the days before every terminal had a mouse ... back then I put my hands on the keyboard at the start of the day and they stayed there the entire day all window navigation was done via the keyboard ... I lost all of that once I started doing development in Smalltalk... Anyway that about covers todays "ideas from the shower"... Dale

6 11