May 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Transcript does not handle multiple thread access

by FranÃ§ois Tanguy

Hello, try this in a workspace (image 10319) : "First open a Transcript via the world menu" Transcript clear. 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] Behavior is bad. Now, try the following: Transcript clear. Transcript open. 5 timesRepeat: [ [Transcript show: 'Hello'] fork ] It is always working. Is it a known problem ? Should we open an issue ? FranÃ§ois

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Lukas Renggli

> Full compliance, on the other hand, is not a primary goal. ANSI Smalltalk is nominal. Too minimal for many tasks, and still people build their frameworks on these foundations to keep their code portable across platforms. If you undermine the Smalltalk standard, Pharo simply can't be the choice for open-source development anymore. Full ANSI compliance must a primary goal. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

May 28, 2009

Re: [Pharo-project] a request for OB

by Alexandre Bergel

> Or considering a loaded package as a modified package, ie. showing > it in the same list at > the top? yes Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by StÃ©phane Ducasse

Yes. The key problem with lot of packages is that they can rot and be forgotten. I think that at one point we should arrive to a system where lot of code is in package but we work on a system where they are automatically/ easily loadable. Stef On May 28, 2009, at 10:02 PM, Adrian Lienhard wrote: > > On May 28, 2009, at 21:41 , John McIntosh wrote: > >> Well I think a statement of direction is required. Is *all* ANSI >> specific >> logic going to be in the base Pharo? Is base Pharo going to be >> ANSI compliant ? >> I don't think people want to load chunks of it from here and there, >> assuming >> they know they need to do that. > > I see it like this: > > - keep already existing ANSI compliant behavior > - where appropriate, fix semantics to be compliant > - where appropriate, add new ANSI behavior > > Full compliance, on the other hand, is not a primary goal. > > Cheers, > Adrian > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 28, 2009

[Pharo-project] [ANN] 10320

by StÃ©phane Ducasse

- Issue 830: invalid utf8 in change log. the attached cs makes the new change file being opened with a FileStream (instead of StandardFileStream). Fix another case where wrong stream class was used. (Unreleated in this cs: delete an unused method in WideString). - Issue 851: allObjectsDo: broken

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Adrian Lienhard

On May 28, 2009, at 21:41 , John McIntosh wrote: > Well I think a statement of direction is required. Is *all* ANSI > specific > logic going to be in the base Pharo? Is base Pharo going to be > ANSI compliant ? > I don't think people want to load chunks of it from here and there, > assuming > they know they need to do that. I see it like this: - keep already existing ANSI compliant behavior - where appropriate, fix semantics to be compliant - where appropriate, add new ANSI behavior Full compliance, on the other hand, is not a primary goal. Cheers, Adrian

May 28, 2009

Re: [Pharo-project] a request for OB

by David RÃ¶thlisberger

Hi Alex, > When I load a Monticello package, I would really love to see it at the > top of the list. Maybe a we could have > 1 - Modified packages > 2 - Loaded Packages > 3 - Base system ok, I could do this. Or considering a loaded package as a modified package, ie. showing it in the same list at the top? David

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by John McIntosh

Well I think a statement of direction is required. Is *all* ANSI specific logic going to be in the base Pharo? Is base Pharo going to be ANSI compliant ? I don't think people want to load chunks of it from here and there, assuming they know they need to do that. On Thu, May 28, 2009 at 12:30 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

May 28, 2009

Re: [Pharo-project] SLICE-RelicensingPart1

by Adrian Lienhard

On May 28, 2009, at 18:16 , Lukas Renggli wrote: >> I am aware this is part of ANSI. My thought behind my email was that >> if nobody uses it, then this method could be moved into a package >> ANSI >> that can be separately loaded. > > Cool, then we also get rid of OrderedCollection? So you are saying that nobody is using OrderedCollection? But seriously, this sort of mails are unhelpful. Adrian

May 28, 2009

[Pharo-project] Testing SmartRefStream...

by Stephan Eggermont

Creates a lot of newlines on the mailing list. Sorry about that. My mail program didn't show the charactres at all. Stephan

May 28, 2009