- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Removing ReferenceStream

by Esteban Lorenzano

+1 On 05/06/2012, at 22:18, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. Right now ReferenceStream is deprecated, not removed. In another thread, I asked about cleaning DataStream and let it ONLY for Monticello. That way we can really simplify DataStream, remove DiskProxy and much more. For more details see: http://code.google.com/p/pharo/issues/detail?id=6036. Then whoever need a serializer, it can use Fuel which is already integrated. > The problem is that keeping ReferenceStream as deprecated means that it has to run...meaning that I cannot remove nothing but deprecate everything...DataStream has extension methods in about 20 classses...meaning I have to rename 20 protocols from *SystemObject Storage to *Depreacted20. Apart from even more work is needed to keep it "alive". > > So...sometimes it is really hard to keep everything as deprecated. We don't have manpower enough to keep everything 100% deprecated 100% of the time. Fuel works out of the box from Pharo 1.1 to 2.0 so if anybody needs to move data from previous images, he can use Fuel. Not sure how many people is using ReferenceStream but I have been founding bugs in the last years that nobody even reported.. > > So, can I remove ReferenceStream? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com >

June 5, 2012

Re: [Pharo-project] Removing ReferenceStream

by Pavel Krivanek

AFAIK there is common consensus that some things will be removed from 2.0 without deprecation. When we offer more than adequate replacement for ReferenceStream in form of Fuel, I think that we can remove it without doubts. -- Pavel On Tue, Jun 5, 2012 at 10:18 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. Right now ReferenceStream is deprecated, not removed. In another > thread, I asked about cleaning DataStream and let it ONLY for Monticello. > That way we can really simplify DataStream, remove DiskProxy and much more. > For more details see: http://code.google.com/p/pharo/issues/detail?id=6036. > Then whoever need a serializer, it can use Fuel which is already integrated. > The problem is that keeping ReferenceStream as deprecated means that it has > to run...meaning that I cannot remove nothing but deprecate > everything...DataStream has extension methods in about 20 classses...meaning > I have to rename 20 protocols from *SystemObject Storage to *Depreacted20. > Apart from even more work is needed to keep it "alive". > > So...sometimes it is really hard to keep everything as deprecated. We don't > have manpower enough to keep everything 100% deprecated 100% of the time. > Fuel works out of the box from Pharo 1.1 to 2.0 so if anybody needs to move > data from previous images, he can use Fuel. Not sure how many people is > using ReferenceStream but I have been founding bugs in the last years that > nobody even reported.. > > So, can I remove ReferenceStream? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com >

June 5, 2012

[Pharo-project] Removing ReferenceStream

by Mariano Martinez Peck

Hi guys. Right now ReferenceStream is deprecated, not removed. In another thread, I asked about cleaning DataStream and let it ONLY for Monticello. That way we can really simplify DataStream, remove DiskProxy and much more. For more details see: http://code.google.com/p/pharo/issues/detail?id=6036. Then whoever need a serializer, it can use Fuel which is already integrated. The problem is that keeping ReferenceStream as deprecated means that it has to run...meaning that I cannot remove nothing but deprecate everything...DataStream has extension methods in about 20 classses...meaning I have to rename 20 protocols from *SystemObject Storage to *Depreacted20. Apart from even more work is needed to keep it "alive". So...sometimes it is really hard to keep everything as deprecated. We don't have manpower enough to keep everything 100% deprecated 100% of the time. Fuel works out of the box from Pharo 1.1 to 2.0 so if anybody needs to move data from previous images, he can use Fuel. Not sure how many people is using ReferenceStream but I have been founding bugs in the last years that nobody even reported.. So, can I remove ReferenceStream? thanks -- Mariano http://marianopeck.wordpress.com

June 5, 2012

[Pharo-project] String printOn: / storeOn:

by Camillo Bruni

I think that printing on streams could be improved by changing String >> #printOn: to printOn: aStream aStream nextPutAll: self because string is special when printing: String streamContents: [ :s| s print: 'asdf'] does NOT equal: String streamContents: [ :s| s nextPutAll: 'asdf' asString ] whereas String streamContents: [ :s| s print: 1] equals: String streamContents: [ :s| s nextPutAll: 1 asString ] so for any other object s nextPutAll: object asString equals s print: object Now the same implication holds for Symbol and most probably this idea is in strong contrast to the blue book :D

June 5, 2012

Re: [Pharo-project] Trouble loading XML RPC

by garduino

Ni Noury: >Actually, I get only tests from xml rpc with your procedure. >I thought there might be a way to get all tests for all required packages, to test their compatibility with >Pharo 2.0 >But, it seems that I have to load them by hand. Ahh, but is not posible to make the load modifying the configurationof? > Any way, I tried on Pharo 2.0. There is the issue of underscores, but this > is no big deal. I should re-check all the code (lot of parts are form older versions). >The good news is that the client side seems to work. At least the tests are green for parts that does not >rely on a local server (XMLRPCTest is red!). >Tests with Flicker do pass. Yes, the client side seems to work ok. Let me polish some more things. >There is however XMLROCDecoderTest>>#testDecoder that fails. The reason is that now Pharo does >take care of nanoseconds, but the encoder does not handle it. >I guess this is not supported in the protocol. Isn't it? So, I propose to fix it but putting nanoseconds to >zero >XMLRPCDateAndTime>>time: t > "set the time portion of the datetime." > time := Time fromSeconds: t seconds truncated Nice catch! I tried and Works ok. I think that will not generate any problem with the protocol. I can publish with some things I'm improving in the code if you agree. By other hand, the Transcript error at load time, have you experienced it? Is something related with some new thing in 1.4 ? I've not checked yet. Cheers and thanks by the cooperation! -- View this message in context: http://forum.world.st/Trouble-loading-XML-RPC-tp4632653p4633389.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 5, 2012

Re: [Pharo-project] [update 2.0] #20110

by Nicolas Cellier

To illustrate that these dumb tests that don't look that interesting might sometimes help, here is how I changed Integer>>/ aNumber "Refer to the comment in Number / " | quoRem | aNumber isInteger ifTrue: [quoRem := self digitDiv: aNumber abs "*****I've added abs here*****" neg: self negative ~~ aNumber negative. (quoRem at: 2) = 0 ifTrue: [^ (quoRem at: 1) normalize] ifFalse: [^ (Fraction numerator: self denominator: aNumber) reduced]]. aNumber isFraction ifTrue: [| n d | n := self // (d := self gcd: aNumber numerator). d := aNumber numerator // d. ^d = 1 ifTrue: [n * aNumber denominator * d] ifFalse: [Fraction numerator: n * aNumber denominator denominator: d]]. ^ aNumber adaptToInteger: self andSend: #/ But hey, we can't fail on such trivial method, can we? Unless... maybe the cyclomatic complexity isn't that low after all... Please, could you tell me where the error was ? Nicolas 2012/6/5 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > 2012/6/5 Sven Van Caekenberghe <sven(a)beta9.be>: >> Haha, very funny. >> >> It's a good thing there are so many jokes hidden inside the image. >> >> We could add a couple/many more: >> >> self deny: 1 = 2. >> self deny: 1 = -1. >> self deny: (4 / 2) = 3 >> self shouldnt: [ 1 / 2 ] raise: ZeroDivide >> >> ;-) >> > > Yes it's laughable. > However, I recently hacked Intger/Fraction to speed up mixed > operations and guess what... > once you know the miserable error's we can make... > > Nicolas > >> On 05 Jun 2012, at 12:10, Serge Stinckwich wrote: >> >>> On Tue, Jun 5, 2012 at 5:04 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>>> On Tue, Jun 5, 2012 at 11:55 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>>>> testGeneralInquiries >>>>>> Â Â Â | now d t dt | >>>>>> >>>>>> Â Â Â now Â := self timeClass dateAndTimeNow. >>>>>> Â Â Â self >>>>>> Â Â Â Â Â Â Â assert: now size = 2; >>>>>> Â Â Â Â Â Â Â assert: now last <= self timeClass now. >>>>>> >>>>>> Â Â Â self should: [ self timeClass timeWords ] raise: MessageNotUnderstood. >>>>>> >>>>>> Â Â Â d := '2 June 1973' asDate. >>>>>> Â Â Â t := '4:02:47 am' asTime. >>>>>> Â Â Â dt := self timeClass dateAndTimeFromSeconds: (2285280000 + 14567). >>>>>> Â Â Â self >>>>>> Â Â Â Â Â Â Â assert: dt = {d. t.}. >>>>>> >>>>>> >>>>>> The middle part is a GREAT example of a useful unit testâ¦ >>>>> >>>>> that's called a negative test :D, assume what possible could fail in the universe and test for it :D >>>> >>>> I will write a paper on automatic negative test generation. Who wants >>>> to join? :-) >>> >>> You can even write a program that write a paper about negative tests >>> generation ;-) >>> >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >>> >> >>

June 5, 2012

Re: [Pharo-project] [update 2.0] #20111

by Benjamin

It's green on my image :s I will investigate this evening, but in the mid-time I have posted a new version of Spec-Core :) BTW< Marcus already opened a bug entry: http://code.google.com/p/pharo/issues/detail?id=6029 Thank both of you, Ben On Jun 5, 2012, at 11:25 AM, Pavel Krivanek wrote: > We have one more failing tests: > Spec.Tests.SpecInterpreterTest.testBuildWindowFor > > -- Pavel > > On Tue, Jun 5, 2012 at 2:22 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> 20111 >> ----- >> >> Issue 6027: PackageServices is unused and undocumented >> http://code.google.com/p/pharo/issues/detail?id=6027 >> >> Issue 6028: fix typo in #printPrimitiveOn: >> http://code.google.com/p/pharo/issues/detail?id=6028 >> >> Issue 6026: New version of Spec 0.4 >> http://code.google.com/p/pharo/issues/detail?id=6026 >> >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> >

June 5, 2012

Re: [Pharo-project] [update 2.0] #20111

by Pavel Krivanek

We have one more failing tests: Spec.Tests.SpecInterpreterTest.testBuildWindowFor -- Pavel On Tue, Jun 5, 2012 at 2:22 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20111 > ----- > > Issue 6027: Â Â PackageServices is unused and undocumented > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=6027 > > Issue 6028: Â Â fix typo in #printPrimitiveOn: > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=6028 > > Issue 6026: Â Â New version of Spec 0.4 > Â Â Â Â http://code.google.com/p/pharo/issues/detail?id=6026 > > > > -- > Marcus Denker -- http://marcusdenker.de > >

June 5, 2012

Re: [Pharo-project] About Seed, Hazelnut and related

by Guillermo Polito

On Tue, Jun 5, 2012 at 4:30 PM, Ben Coman <btc(a)openinworld.com> wrote: > Edgar J. De Cleene wrote: > >> >From the excellent blog http://playingwithobjects.**wordpress.com/<http://playingwithobjects.wordpress.com/> Guille >> was doing we read >> >> The results of the project so far are: >> * It can create an Smalltalk image living inside another image. >> >> > This sounds useful to my earlier question to mixing open and closed source. > > But this is not *yet* analized in security terms... :)

June 5, 2012

Re: [Pharo-project] About Seed, Hazelnut and related

by Guillermo Polito

On Tue, Jun 5, 2012 at 1:40 PM, Edgar J. De Cleene <edgardec2005(a)gmail.com>wrote: > From the excellent blog http://playingwithobjects.wordpress.com/ Guille was doing we read > > The results of the project so far are: > > - It can create an Smalltalk image living inside another image. > - This inner/guest image can be written in a new .image file. > - With this approach a small kernel of 1.1MB has been reached. > - SpaceTally runs and prints reports to understand how the space is > distributed among objects. > - A tool to detect every uninitialized class variable/class instance > variable and references to unexistant globals was developed. > > > > I like to know exact steps for doing this, so maybe can feedback some.. > Most of these results are based on military secret experiments :). I'll open the stuff soon, very soon, so you can break as much as you wish yourself :). So far, tomorrow there will be a new blog post with updates on the project. > > Guille: > Buenisimo lo que estas haciendo. > Y como ya los tenemos a Esteban, Igor, Santiago , te esperamos > http://ar.groups.yahoo.com/group/squeakRos/ > > Edgar >

June 5, 2012