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

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Denis Kudriashov

Perfect! 19 Ð¼Ð°Ñ 2015 Ð³. 7:49 Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°ÑÐµÐ»Ñ "Marcus Denker" <marcus.denker(a)inria.fr> Ð½Ð°Ð¿Ð¸ÑÐ°Ð»: > > On 13 May 2015, at 11:21, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Thanks's Marcus. It is beautiful thing. > > Is parsing locate errors by "dot"s? I mean how it will parse "3+. 1+2"? It > will be super cool if we have only "3+." as error but remains code as good > one > > > You can just look at > > OpalCompiler new > source: 'method 3+. 1+2'; > useFaultyForParsing: true; > parse. > > with the GT inspector, it has a very nice AST view: > > >

May 21, 2015

Re: [Pharo-dev] about the donwload win.zip pharo 40

by Marcus Denker

> On 20 May 2015, at 20:46, stepharo <stepharo(a)free.fr> wrote: > > Hi > > one student of saint-louis tried to download pharo from the pharo web site > and on windows the archive seems broken. > > Could someone try and let me know? It could be related to the CDN cacheâ¦ I am thinking of turning it off. Marcus

May 21, 2015

Re: [Pharo-dev] Critics Browser should diff formatted original

by Sean P. DeNigris

Sean P. DeNigris wrote > Issue 15574: Critics: Ignore whitespace changes when diffing > transformations > https://pharo.fogbugz.com/default.asp?15574 Thanks to Yuriy, now the confusing diff on the left will look like the one on the right <http://forum.world.st/file/n4827759/Screenshot_2015-05-21_00.png> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Critics-Browser-should-diff-formatted-original-tp4827… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 21, 2015

Re: [Pharo-dev] Null Coalesce Operator?

by Eliot Miranda

Hi Aliaksei, On Wed, May 20, 2015 at 12:55 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Check for the nil value should be banned in my opinion. There are >> well-known techniques to not have to use it (e.g., Null-object pattern). > > Absolutely agree! :) > > My only fear is that it could encourage the use of nil instead of proper >> Null Objects > > Sometimes it's impossible to always have Null Object in first place and we > still have to do something like this: > > default1 ifNil: [ "Null object" ]. > > > I even saw in many places > > values >> ^ values ifNil: [ OrderedCollection new ] > > > And it perfectly works. However, usage of blocks for such simple checks > looks like overhead, isn't it? (and for modern kids it looks ugly too). > Take a look how many languages already support ??: > C#, Swift, PHP7 (yes, these php-coders had to wait until 7th version), > JavaScript, Groovy (they name it Evil Operator), Objective-C. > > But yes, nils are evil :) > > Blocks are of course better, because they are lazy and don't get executed > if value is not nil - complete opposite to null coalescing operator. > ifNil:, ifNotNil:, ifNotNil:ifNil: and ifNil:ifNotNil: all get inlines as per ifTrue: et al, so no blocks are created The only overhead is syntactic. > > Cheers, > Alex > > On Wed, May 20, 2015 at 9:41 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> Yes, #ifNil: is almost the same (except the #value): >> >> |default1 default2 default3 default4 | >> default1 := nil. >> default2 := nil. >> default3 := 'foo'. >> default4 := 'don''t care'. >> default1 ifNil: [ default2 ifNil: [ default3 ifNil: [ default4 ] ] ] >> >> => 'foo' >> >> > On 20 May 2015, at 21:38, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> > >> > â¦ifNone: is a nice idiom, but not always available (in which case, we >> should think about introducing it) >> > >> > ?? is basically an infix but eager version of #ifNil:, IMHO a pragmatic >> thing to have; could be quite handy. >> > My only fear is that it could encourage the use of nil instead of >> proper Null Objectsâ¦ and here we start bikeshedding >> > >> > On 20 May 2015 at 21:31, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: >> > >> > In my experience those situations end up been handled by collections, >> detect:ifNone: which even handles the case when all defaults are nil. >> > >> > But maybe that idiom is very common in another situations. >> > >> > >> > >> > -- >> > Damien Pollet >> > type less, do more [ | ] http://people.untyped.org/damien.pollet >> >> >> > -- best, Eliot

May 21, 2015

Re: [Pharo-dev] New Collections for Pharo

by Sergio Fedi

I agree with Hernan. In the MultiValueDictionary sometimes it's necessary to parametrize the collection the value has. On Wed, May 20, 2015 at 8:30 PM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hello Alexander, > > For the MultiValueDictionary IMHO you can need to use other Collections > beside OrderedCollection, so you can replace #asOrderedCollection with > #asSortedCollection, etc adding an inst. var. storing the converting > selector could result in a more flexible Collection. > > I know at least 2 other BTree Smalltalk implementations out there, one > fron Avi Bryant and another one here > http://www.virtualmachinery.com/btreestqstart.htm . Have you reviewed > them? > > On the other hand, do you have some examples or empirical benchmarks to > share? > > Cheers, > > HernÃ¡n > > > 2015-05-20 2:12 GMT-03:00 ÐÐ»ÐµÐºÑÐ°Ð½Ð´Ñ ÐÑÐµÐ½ÑÐµÐ² <pharo-dev(a)lists.pharo.org>: > >> >> >> ---------- Mensaje reenviado ---------- >> From: "ÐÐ»ÐµÐºÑÐ°Ð½Ð´Ñ ÐÑÐµÐ½ÑÐµÐ²" <alexzund3r(a)yahoo.com> >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Cc: >> Date: Wed, 20 May 2015 05:12:29 +0000 (UTC) >> Subject: New Collections for Pharo >> Greetings to everyone. As you remember, i was working at some new >> collections for Pharo Smalltalk. Today i want to share some results with >> the community. There are three collections currently implemented: >> >> 1. MultiValueDictionary - a dictionary which holda a pairs of "Key -> >> (Val1. Val2 ..)" >> 2. CircularLinkedList - a linked list which have additional pointer >> from its tail to head >> 3. Btree (do not forget to set the degree by sending the "degree:" >> message before start working. Also removing keys doesn't work correctly in >> some cases) >> >> Comments, suggestions and critics are very appreciatied, because you are >> my target audience. >> Collections are availiable for download on my project page: SmalltalkHub >> <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> >> >> >> >> >> >> >> SmalltalkHub <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> >> Loading. Please wait. >> ÐÑÐ¾ÑÐ¼Ð¾ÑÑÐµÑÑ Ð½Ð° smalltalkhub.com >> <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> >> ÐÑÐµÐ´Ð²Ð°ÑÐ¸ÑÐµÐ»ÑÐ½ÑÐ¹ Ð¿ÑÐ¾ÑÐ¼Ð¾ÑÑ Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Yahoo >> >> (NewCollections,NewCollectionsTest and NewCollectionsSupport packages >> you need) >> >> Best wishes >> Alexander >> >> >> >

May 20, 2015

Re: [Pharo-dev] New Collections for Pharo

by HernÃ¡n Morales Durand

Hello Alexander, For the MultiValueDictionary IMHO you can need to use other Collections beside OrderedCollection, so you can replace #asOrderedCollection with #asSortedCollection, etc adding an inst. var. storing the converting selector could result in a more flexible Collection. I know at least 2 other BTree Smalltalk implementations out there, one fron Avi Bryant and another one here http://www.virtualmachinery.com/btreestqstart.htm . Have you reviewed them? On the other hand, do you have some examples or empirical benchmarks to share? Cheers, HernÃ¡n 2015-05-20 2:12 GMT-03:00 ÐÐ»ÐµÐºÑÐ°Ð½Ð´Ñ ÐÑÐµÐ½ÑÐµÐ² <pharo-dev(a)lists.pharo.org>: > > > ---------- Mensaje reenviado ---------- > From: "ÐÐ»ÐµÐºÑÐ°Ð½Ð´Ñ ÐÑÐµÐ½ÑÐµÐ²" <alexzund3r(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Wed, 20 May 2015 05:12:29 +0000 (UTC) > Subject: New Collections for Pharo > Greetings to everyone. As you remember, i was working at some new > collections for Pharo Smalltalk. Today i want to share some results with > the community. There are three collections currently implemented: > > 1. MultiValueDictionary - a dictionary which holda a pairs of "Key -> > (Val1. Val2 ..)" > 2. CircularLinkedList - a linked list which have additional pointer > from its tail to head > 3. Btree (do not forget to set the degree by sending the "degree:" > message before start working. Also removing keys doesn't work correctly in > some cases) > > Comments, suggestions and critics are very appreciatied, because you are > my target audience. > Collections are availiable for download on my project page: SmalltalkHub > <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> > > > > > > > SmalltalkHub <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> > Loading. Please wait. > ÐÑÐ¾ÑÐ¼Ð¾ÑÑÐµÑÑ Ð½Ð° smalltalkhub.com > <http://smalltalkhub.com/#!/~OBrenchev/NewPharoCollections> > ÐÑÐµÐ´Ð²Ð°ÑÐ¸ÑÐµÐ»ÑÐ½ÑÐ¹ Ð¿ÑÐ¾ÑÐ¼Ð¾ÑÑ Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Yahoo > > (NewCollections,NewCollectionsTest and NewCollectionsSupport packages > you need) > > Best wishes > Alexander > > >

May 20, 2015

Re: [Pharo-dev] about the donwload win.zip pharo 40

by stepharo

tx you all! S Le 20/5/15 19:54, Max Leske a Ã©crit : >> On 20 May 2015, at 20:46, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> one student of saint-louis tried to download pharo from the pharo web site >> and on windows the archive seems broken. >> >> Could someone try and let me know? > Works perfectly on Win 8 (Virtualbox). The only thing I can think of is that someone might try to open the archive unpacked (which will promt for the image file). So it is definitely not corrupt. > > Cheers, > Max > >> Tx. >> >> Stef >> > >

May 20, 2015

MongoTalk UpdateOperation and options. How to?

by phil＠highoctane.be

In MongoTalk, there is UpdateOperation. But I can't find how one can do an update with options. http://docs.mongodb.org/manual/reference/method/db.collection.update/ I see Mongo>>update: origDictionary with: newDictionary collection: aString (UpdateOperation collection: aString id: self nextRequestID stream: stream originalObject: origDictionary newObject: newDictionary) write But there is no room for "options" I tried to do it with commands but wasn't able to figure out how. In MongoShell, db.runCommand({ "update":"Message", "query":{}, "updates": [{"$set": {"READ":true} }], "options": {"multi":true} }) gives me "missing q parameter" Anyone knowing how to do this? I've also done this code: | query what | query := { } asDictionary. what := { 'READ' -> true } asDictionary. Mapless currentRepository database beLogging. (Mapless currentRepository collection: Message) "<<- basically one gets a Mongoclient doing the updata:with:" update: query with: {'$set' -> what } asDictionary. Thanks for any help :-) Phil

May 20, 2015

Re: [Pharo-dev] Null Coalesce Operator?

by Alexandre Bergel

Hi! I perfectly understand the purpose of this method "??â Although I do not think this will seriously impact the quality of the code being produced, I still believe it will not help making code of a better quality. Check for the nil value should be banned in my opinion. There are well-known techniques to not have to use it (e.g., Null-object pattern). Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 20, 2015, at 3:19 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi, > > Null coalesce operator - returns the first not nil operand. > http://en.wikipedia.org/wiki/Null_coalescing_operator <http://en.wikipedia.org/wiki/Null_coalescing_operator> > > Adding one simple method to an Object: > > ?? anObject > ^ self > > and to UndefinedObject: > > ?? anObject > ^ anObject > > could allow us to write: > > default1 := nil. > default2 := nil. > default3 := 'foo'. > default4 := 'don''t care'. > config := default1 ?? default2 ?? default3 ?? default4. > > => 'foo' > > I know you don't like to add new methods to an object, but still :) >

May 20, 2015

Re: [Pharo-dev] Null Coalesce Operator?

by Aliaksei Syrel

Yes, let's not introduce it :) Not a smalltalk way! Cheers, Alex On Wed, May 20, 2015 at 10:27 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > On Wed, May 20, 2015 at 10:14 PM, Chris Cunningham < > cunningham.cb(a)gmail.com> wrote: > >> would generate a new OrderedCollection every time it is called!. Even >> more overkill. > > > Last line from previous email: > Blocks are of course better, because they are lazy and don't get executed > if value is not nil - complete opposite to null coalescing operator. > > That is the price that should be payed. > > Cheers, > Alex > >

May 20, 2015