November 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] #at:ifAbsent: for Array(s) could be faster

by Igor Stasenko

Here the original implementation, which Array inherits from SequenceableCollection: at: index ifAbsent: exceptionBlock "Answer the element at my position index. If I do not contain an element at index, answer the result of evaluating the argument, exceptionBlock." (index between: 1 and: self size) ifTrue: [^ self at: index]. ^ exceptionBlock value the thing is, that #at: primivite also doing a range checking and fails if index is invalid, so if index is valid, as result we performing a range checking twice instead of just once. Here the simple implementation how to make things faster: fat: index "Primitive. Assumes receiver is indexable. Answer the value of an indexable element in the receiver. Fail if the argument index is not an Integer or is out of bounds. Essential. See Object documentation whatIsAPrimitive. Read the class comment for a discussion about that the fact that the index can be a float." <primitive: 60> ^ #plopp fat: index ifAbsent: aBlock | x | x := (self fat: index). x == #plopp ifTrue: [ ^ aBlock value ]. ^ x And speedup is almost 2 times: [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 1 ifAbsent: nil ] ] timeToRun 39 [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 1 ifAbsent: nil ] ] timeToRun 20 Even when index is out of range, it is still much faster: [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) at: 100 ifAbsent: nil ] ] timeToRun 35 [ 1000000 timesRepeat: [ #(1 2 4 5 56 67 67) fat: 100 ifAbsent: nil ] ] timeToRun 24 The problem, of course, that trick with #plopp is a dirty hack. Because if array include an #plopp object as element, it will report as it absent, instead of answering it. There is no way to ensure that any arbitrary object are never included as element in array, so this is no-go for generic replacement. But in controlled environment, when you know that none of arrays which you using with #fat:ifAbsent: will ever include #plopp (or pick your own unique object) it may be a good alternative. -- Best regards, Igor Stasenko.

Nov. 2, 2011

Re: [Pharo-project] Small tool to edit bloc code

by Igor Stasenko

On 2 November 2011 08:46, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > From DrGeo I would like the user to edit Smalltalk code in the form of > block of code. > The user interface I need is maninly to let the user write and compile > code. When compiled, DrGeo should get a notification to fetch the code > for internal use. > > What is the best candidate to do that ? hmm.. i am a bit confused by question. In morphic you need to create an editor morph and then hook on 'accept' or 'ok' button to send the text to compiler. You can use compiler's #compileNoPattern: textOrStream in: aClass context: aContext notifying: aRequestor ifFail: failBlock to compile a code without method header (doits) and then install the result at class you choose. > > Hilaire > > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > > > -- Best regards, Igor Stasenko.

Nov. 2, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Igor Stasenko

On 2 November 2011 15:42, Max Leske <maxleske(a)gmail.com> wrote: > Static git repository of the source code of Squeak and Pharo until Squeak version 4 and Pharo 1: > http://scg.unibe.ch/research/Pharogenesis > https://github.com/pharogenesis > > The source code layout (tree of directories and files) could probably be better. But I guess one could use it as proof of concept. > Ah, so you will be second one :) I meant another project in mind. There was a ?thesis? of some student to store all source code in sql database. instead of .changes and .source files integrated into an image. > Max > > > > On 02.11.2011, at 15:27, Igor Stasenko wrote: > >> How about new source code management? >> >> In terms of: >> - better abstraction of source code access in image >> - create a shared repository (database) , which can be used to browse >> the history of all source code of Pharo and its predecessor up to >> Squeak 1.0. >> >> We are discussed this idea couple times, and we already having some >> pieces of puzzle , like Ring. >> Also, there is already a project made by someone (forgot the name) , >> who already storing all source code in database and managing it there. >> >> -- >> Best regards, >> Igor Stasenko. >> > > > -- Best regards, Igor Stasenko.

Nov. 2, 2011

Re: [Pharo-project] curl?

by Sven Van Caekenberghe

Sebastian, On 01 Nov 2011, at 20:50, Sebastian Sastre wrote: > how can I use curl from the image? > where is the code I should install? Why do you need curl ? (Not that curl isn't a great tool, mind you). Unless you need some feature that is not supported by any of the HTTP clients I would always use a pure Smalltalk solution: it is less hassle and you can read/manipulate the implementation. Note that there are already some people who successfully used the Zinc+Zodiac combination to do HTTPS. Regards, Sven

Nov. 2, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Max Leske

Static git repository of the source code of Squeak and Pharo until Squeak version 4 and Pharo 1: http://scg.unibe.ch/research/Pharogenesis https://github.com/pharogenesis The source code layout (tree of directories and files) could probably be better. But I guess one could use it as proof of concept. Max On 02.11.2011, at 15:27, Igor Stasenko wrote: > How about new source code management? > > In terms of: > - better abstraction of source code access in image > - create a shared repository (database) , which can be used to browse > the history of all source code of Pharo and its predecessor up to > Squeak 1.0. > > We are discussed this idea couple times, and we already having some > pieces of puzzle , like Ring. > Also, there is already a project made by someone (forgot the name) , > who already storing all source code in database and managing it there. > > -- > Best regards, > Igor Stasenko. >

Nov. 2, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Igor Stasenko

How about new source code management? In terms of: - better abstraction of source code access in image - create a shared repository (database) , which can be used to browse the history of all source code of Pharo and its predecessor up to Squeak 1.0. We are discussed this idea couple times, and we already having some pieces of puzzle , like Ring. Also, there is already a project made by someone (forgot the name) , who already storing all source code in database and managing it there. -- Best regards, Igor Stasenko.

Nov. 2, 2011

Re: [Pharo-project] Comment Syntax

by Igor Stasenko

On 1 November 2011 18:08, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Mon, Oct 31, 2011 at 2:22 PM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> The problem is that both #/* and #/* are valid binary operators, so >> they don't work well for comments. >> >> I don't really remember what I proposed a few years ago, although I >> remember that exactly the same proposal was made. What would work is >> to use something like "* and *" (or any other double thing that starts >> with a double quote). Like this the comments could contain double >> quotes. > > Gilad Bracha chose (* & *) for Newspeak. Â These are not valid binary > selectors and * can't follow ( in valid code. Â A good choice. > Hehe. Pascal has the same syntax for comments. >> >> As a short term solution you can also put your comments into single >> quotes. Unused string literals are removed by the compiler. >> >> Lukas >> >> On 31 October 2011 22:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> > Me too. >> > >> > Sean lukas proposed a syntax for that in the mailing-list a year ago. >> > If you find it please resent it. >> > >> > Stef >> > >> > On Oct 31, 2011, at 9:12 PM, Sean P. DeNigris wrote: >> > >> >> Would it be difficult/valuable to create an alternate comment syntax? I >> >> often >> >> find myself wanting to comment a large block itself containing >> >> comments. It >> >> would be nice to have something like C++'s /* */. I feel like this may >> >> have >> >> been brought up before, but couldn't find it searching the lists. >> >> >> >> Sean >> >> >> >> -- >> >> View this message in context: >> >> http://forum.world.st/Comment-Syntax-tp3961451p3961451.html >> >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> >> > >> > >> > >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > best, > Eliot > -- Best regards, Igor Stasenko.

Nov. 2, 2011

Re: [Pharo-project] curl?

by Henrik Sperre Johansen

On 02.11.2011 12:31, Sean P. DeNigris wrote: > p := PipeableOSProcess command: 'curl "http://google.com"'. > p output. > > -- > View this message in context: http://forum.world.st/curl-tp3972448p3972641.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > There is also a plugin in (some?) vm's calling curl directly, whose image-side glue is part of the package found at: http://www.squeaksource.com/CurlPlugin.html (Class Curl afaict) Cheers, Henry

Nov. 2, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Norbert Hartl

Am 31.10.2011 um 11:54 schrieb StÃ©phane Ducasse: > Now the free items with probably igor involvement > - Multiwindowing support > - Fully working multithreaded FFI with ***Documentation*** > - Filesystem fix and integration > - Integration of OPAL > - RPackage integration I like to add environments so we can have multiple versions in the same image and get rid of default global state. I think you have that already on your mind even with separate object memories. Norbert

Nov. 2, 2011

Re: [Pharo-project] curl?

by Sean P. DeNigris

p := PipeableOSProcess command: 'curl "http://google.com"'. p output. -- View this message in context: http://forum.world.st/curl-tp3972448p3972641.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 2, 2011