- Pharo-dev - lists.pharo.org

help needed with fixing the SpecDebugger
by Tudor Girba Nov. 14, 2013

Nov. 14, 2013

Hi, I need a bit of help with the issue of the SpecDebugger relying on the default inspector being implemented in Spec. I investigated a bit, but now I am stuck. Details here: https://pharo.fogbugz.com/f/cases/12055/ Can anyone look at it? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 6

Instrumenting field accesses with Opal?
by Alexandre Bergel Nov. 13, 2013

Nov. 13, 2013

Hi! Is there a way to get notified when fields are accessed? That would be awesome Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

6 8

Fwd: In-memory FileSystem write streams not being polymorphic
by Nicolas Cellier Nov. 13, 2013

Nov. 13, 2013

---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> Date: 2013/11/13 Subject: Re: [Pharo-dev] In-memory FileSystem write streams not being polymorphic The long answer is simple: the more responsibility you put in Stream, the more complexity you get. The first complexity that I'm speaking of is non-uniformity and random implementation (or un-implementation) of a set of features. I mean some streams in the huge hierarchy implement only half of the contract, but hey, what was the contract exactly? Ah, yes, there were no contract, just hacks left here and there randomly and concurrently in a big hierarchy. I add a new subclass, but don't implement all the features, there are too many of them, and I don't know them all.. I add a new feature, but don't implement it in all the classes, there are too many of them, and I don't know them all. This procedure invariably ends up with a blob of un-maintanable code, were two stream would not even agree on upToEnd behavior - I think you remember it :) If the goal is to replicate all the accumulated responsibilities of Squeak Streams, but with a clarified contract, I think this is a dead end: too much cruft to support, too many features, too many undefined or not well defined behaviors to be clarified. Xtreams takes the opposite path: concentrate on constructing a common, simple and uniform API, concerning streams, just basic stream methods. Some specialized streams then implement some specialized behavior, and you can compose them (by wrapping) when you need the specific API. This way, you ain't got to implement/maintain feature A into a few dozen of classes. And your brand new SpecialFeatureBStream only has to implement a few well known behaviours and your Special Feature B. The short answer is even more simple : a stream does not have a name, like a collection does not have a name, because we ain't gonna need it. If we really need a name, then we'll create a XTNamedReadStream and a XTNamedWriteStream responding to #name, but I doubt we'll do. 2013/11/13 Chris Muller <ma.chris.m(a)gmail.com> > On Wed, Nov 13, 2013 at 9:58 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Yes, a Wrapper would provide the legacy API. >> >> And yes, the name of a stream should better not be part of the API. >> Most stream don't have a name, and adding such API adds all sort of >> un-needed complexity. >> It's an internal detail that can eventually help for reporting error if >> accessible, but nothing more. >> >> > I know nothing about Xtreams but, IMO, this obsession with sterility > borders on mental illness. > > "All sort of un-needed complexity?" That's overstating it a bit, don't > you think? > > So you must really feel stressed that ALL Object's, in fact, have a #name, > huh? I admit this seems to push the limits but... > > what's the point of having any kind of different streams at all then? > It's the _differences_ between them that makes composing them useful. > Compression, encryption, filtering, sockets, files, circular, etc. You > think you'll be able to do all that and get away with all of them having > exactly the same API? > > IMHO working around that, passing extra objects around, sounds more > stressful than letting a stream on a _file_ know its filename.. > > If it really need it, the application certainly can retrieve the name from >> a higher level object (a FIleReference, FileDirectory or whatever). >> > > How does that solution allow uniformity in stream-using code? > > > > > > >> >> >> 2013/11/13 Chris Muller <asqueaker(a)gmail.com> >> >>> On Tue, Nov 12, 2013 at 7:31 AM, Nicolas Cellier >>> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> > It's just a matter of selecting a strategy. I've proposed two: >>> > A) create a wrapper class for legacy Stream compatibility selectors >>> > B) create extensions for Legacy Stream compatibility selectors >>> > My preference goes to A) >>> >>> By wrappers you mean the Xtreams are the innards doing the work and >>> the wrappers providing the legacy API? >>> >>> This would be a great way to test Xtreams. >>> >>> > The legacy support MUST be minimal (next nextPut: nextPutAll: peek >>> upTo: >>> > ...), otherwise we will import all the cruft in Xtream and would go >>> back to >>> > our starting point... >>> > Once the minimal support written (a few hours should be enough), we >>> should >>> > gradually switch each every legacy Stream usage -> Xtream. >>> > >>> > An area which require more work is those Streams that have mixed >>> conventions >>> > (one portion is interpreted as text, another as binary). >>> > In theory that's easy, we just have two streams and they both wrap on >>> a low >>> > level binary stream, but that means we have to be very cautious with >>> buffers >>> > and caches. >>> > >>> > Another area of work is usage of ugly selectors like name (we try to >>> access >>> > the file name from the Stream API, arghh). Those usages are bad and >>> require >>> > a rewrite. >>> >>> Are you saying a FileStream knowing its #name or #filename is bad? >>> >>> >> >

2 2

PharoV20.source
by Alexandre Bergel Nov. 13, 2013

Nov. 13, 2013

Hi! Why not to include this file in the VM? It often happens to me that this place is wrongly placed. When this happens, Pharo just shows a white screen, without letting what is the error. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

7 10

[pharo-project/pharo-core] 80426c: 30570
by GitHub Nov. 13, 2013

Nov. 13, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 80426c3280e89d9e72ab38aac1f75f5353560448 https://github.com/pharo-project/pharo-core/commit/80426c3280e89d9e72ab38aa… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-13 (Wed, 13 Nov 2013) Changed paths: A Keymapping-Core.package/KMCategory.class/instance/associating/removeKeymapEntry_.st A Keymapping-Core.package/KMCategory.class/instance/binding/keymapForShortcut_.st A Keymapping-Core.package/KMDispatcher.class/instance/building/keymapForShortcut_.st A Keymapping-Core.package/KMDispatcher.class/instance/building/removeKeyCombination_.st M Keymapping-Core.package/KMStorage.class/definition.st M Keymapping-Core.package/KMStorage.class/instance/accessing/add_.st A Keymapping-Core.package/KMStorage.class/instance/accessing/keymapForShortcut_.st M Keymapping-Core.package/KMStorage.class/instance/accessing/keymaps.st A Keymapping-Core.package/KMStorage.class/instance/accessing/remove_.st M Keymapping-Core.package/KMStorage.class/instance/initialization/initialize.st A Keymapping-Core.package/extension/Morph/instance/removeKeyCombination_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script226.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30570.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30570 12149 Add support for removing a binding https://pharo.fogbugz.com/f/cases/12149 http://files.pharo.org/image/30/30570.zip

1 0

[pharo-project/pharo-core]
by GitHub Nov. 13, 2013

Nov. 13, 2013

Branch: refs/tags/30570 Home: https://github.com/pharo-project/pharo-core

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Nov. 13, 2013

Nov. 13, 2013

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/Run=run%201,VM=vm,label=linux… 1 regressions found. FileSystem.Tests.Disk.FileHandleTest.testTruncate

1 0

Peek
by Diego Lont Nov. 13, 2013

Nov. 13, 2013

Working on Petit Delphi we found a strange implementation for asPetitStream: Stream>asPetitStream ^ self contents asPetitStream Further investigation showed that the basic peek was not fast enough for Petit Parser, as it is used a lot. So it implemented a "improved unchecked peek": PPStream>peek "An improved version of peek, that is slightly faster than the built in version." ^ self atEnd ifFalse: [ collection at: position + 1 ] PPStream>uncheckedPeek "An unchecked version of peek that throws an error if we try to peek over the end of the stream, even faster than #peek." ^ collection at: position + 1 But in my knowledge a basic peek should be fast. The real problem is the peek in the underlying peek: PositionableStream>peek "Answer what would be returned if the message next were sent to the receiver. If the receiver is at the end, answer nil." | nextObject | self atEnd ifTrue: [^nil]. nextObject := self next. position := position - 1. ^nextObject That actually uses "self next". The least thing one should do is to cache the next object. But isn't there a primitive for peek in a file stream? Because al overriding peeks of PositionableStream have basically the same implementation: reading the next and restoring the state to before the peek (that is slow). So we would like to be able to remove PPStream without causing performance issues, as the only added method is the "improved peek". Stephan and Diego

6 15

Where to download Viva?
by Alexandre Bergel Nov. 13, 2013

Nov. 13, 2013

Viva is an animation framework for Athens -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Where is the FileDirectory-based version of ZnFileSystemUtils?
by Mariano Martinez Peck Nov. 13, 2013

Nov. 13, 2013

Hi Sven, I was seeing your code of ZnFileSystemUtils ... yes... I probably need the same... but I miss the other subclass ;) that one based on FileDirectory. Is this implemented by chance? If true, where can I find it? Thanks! -- Mariano http://marianopeck.wordpress.com

2 2