- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Limbo: a simple shell wrapper for NativeBoost

by Igor Stasenko

On 19 November 2012 17:17, Max Leske <maxleske(a)gmail.com> wrote: > Hi everyone. > > I want to announce the first (and *very* basic) version of Limbo. > Limbo is a simple wrapper around NativeBoost that lets you run commands on the shell (via sh) or directly (no shell expansion). > why you need to wrap around NativeBoost? perhaps a more correct phrasing would be 'using nativeboost'? > To use Limbo you will need the NBCog VM and install NativeBoost into your image (with "NBInstaller install"). You will also need to build the shared library from the archive attached to this e-mail and put it into the "Plugins" directory of the VM (instructions inside the archive). I also attached the xcode project. > > The Limbo repo: > > MCGemstoneRepository > location: 'http://ss3.gemstone.com/ss/Limbo' > user: '' > password: '' > > I am *not* an experienced C coder so there might be some horrible stuff in the box. If you have any suggestions / requests / bug reports or would like to contribute, let me know. > > Disclaimer: > NativeBoost uses direct memory access. I have written Limbo to the best of my memory layout knowledge (I'm quite a n00b there) but cannot and will not guarantee that you might not experience memory leaks or VM crashes (or any type of crash for that matter). This is just a warning, I haven't had any troubles at all with Limbo so far. > Hmm.. what is the C part for? The whole idea of using NativeBoost is to avoid writing a single line of C code. Because if you cannot avoid that, writing a VM plugin turns to be more preferable. But i didn't saw your code yet, so just commenting what on surface :) > > Cheers, > Max > -- Best regards, Igor Stasenko.

Nov. 19, 2012

[Pharo-project] [ANN] Limbo: a simple shell wrapper for NativeBoost

by Max Leske

Hi everyone. I want to announce the first (and *very* basic) version of Limbo. Limbo is a simple wrapper around NativeBoost that lets you run commands on the shell (via sh) or directly (no shell expansion). To use Limbo you will need the NBCog VM and install NativeBoost into your image (with "NBInstaller install"). You will also need to build the shared library from the archive attached to this e-mail and put it into the "Plugins" directory of the VM (instructions inside the archive). I also attached the xcode project. The Limbo repo: MCGemstoneRepository location: 'http://ss3.gemstone.com/ss/Limbo' user: '' password: '' I am *not* an experienced C coder so there might be some horrible stuff in the box. If you have any suggestions / requests / bug reports or would like to contribute, let me know. Disclaimer: NativeBoost uses direct memory access. I have written Limbo to the best of my memory layout knowledge (I'm quite a n00b there) but cannot and will not guarantee that you might not experience memory leaks or VM crashes (or any type of crash for that matter). This is just a warning, I haven't had any troubles at all with Limbo so far. Cheers, Max

Nov. 19, 2012

[Pharo-project] SortedCollection>>=

by Hernan Wilkinson

Hi, I'm a little surprised with the current SortedCollection #= implementation... it is: = aSortedCollection "Answer true if my and aSortedCollection's species are the same, and if our blocks are the same, and if our elements are the same." self species = aSortedCollection species ifFalse: [^ false]. sortBlock = aSortedCollection sortBlock ifTrue: [^ super = aSortedCollection] ifFalse: [^ false] and my surprise is because it compares the sortBlocks that makes the simplest case to fail like this one: (SortedCollection sortBlock: [ :a :b | a < b ]) = (SortedCollection sortBlock: [ :a :b | a < b ]) One could argue that if we remove the sortBlock comparison then : (SortedCollection sortBlock: [ :a :b | a < b ]) = (SortedCollection sortBlock: [ :a :b | a > b ]) would return true... but is that wrong? ... or is the philosophy to use the message #hasEqualElements: on this cases? BTW, VisualWorks implementation is the same as pharo, but the BlockClosure>>= is different and that's why it works as at least I expected :-) Bye, Hernan -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125* Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

Nov. 19, 2012

Re: [Pharo-project] smalltalkhub problems?

by Nicolas Petton

Something's wrong, yes. I'll have a look tomorrow morning. Nico Camillo Bruni <camillobruni(a)gmail.com> writes: > I don't know if that is intended, but I cannot load code from Smalltalkhub currently > > The following file is not found: > > http://smalltalkhub.com/mc/dh83/p/P4-Kernel-CamilloBruni.10.mcz > > even though it's listed here > > http://smalltalkhub.com/mc/dh83/p/main > > > best > cami -- Nicolas Petton http://nicolas-petton.fr

Nov. 19, 2012

[Pharo-project] [update 2.0] #20411

by Marcus Denker

20411 ----- Issue 7006: Obsolete Ref to ChangeSorter http://code.google.com/p/pharo/issues/detail?id=7006 Issue 6928: Obsolete class after running all tests http://code.google.com/p/pharo/issues/detail?id=6928 Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.483.diff -- Marcus Denker -- http://marcusdenker.de

Nov. 19, 2012

Re: [Pharo-project] [NativeBoost] calls to munmap always fail on OS X 10.8.2

by Max Leske

Your fix works like a charm. Thanks! Max On 18.11.2012, at 17:14, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 18 November 2012 12:54, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 18 November 2012 12:41, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> Try loading >>> NativeBoost-Mac-IgorStasenko.7 >>> (and do NBMacConstants initialize, and then restart the image) >>> see if it will fix the issue. >>> >> oh wait. this won't work.. >> i really don't like to use signed values for arguments.. >> > okay, this one should do the work: > > Name: NativeBoost-Core-IgorStasenko.78 > Author: IgorStasenko > Time: 18 November 2012, 5:11:19.289 pm > UUID: 749eb374-06d6-480d-8aeb-6de80c89ce33 > Ancestors: NativeBoost-Core-IgorStasenko.77 > > - use 32-bit complement for negative values in loadModule function. > > (oops.. comment is a bit wrong, it is not loadModule, but loadSymbol.., > but i already commited the code ) > > There is no need for any changes in mac constants (it is better to > keep them negative for future > 64 bit compliance) > > -- > Best regards, > Igor Stasenko. >

Nov. 19, 2012

[Pharo-project] smalltalkhub problems?

by Camillo Bruni

I don't know if that is intended, but I cannot load code from Smalltalkhub currently The following file is not found: http://smalltalkhub.com/mc/dh83/p/P4-Kernel-CamilloBruni.10.mcz even though it's listed here http://smalltalkhub.com/mc/dh83/p/main best cami

Nov. 19, 2012

Re: [Pharo-project] method wrappers package name problem

by Noury Bouraqadi

Hi, I tried MethodWrappers42 under Pharo 2.0-20370. I've got many tests turn green by simply adding CompiledMetod>>#isMwMethodWrapper that return true. Attached the mcz file. BTW, what is the license of this project? Noury Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de necessite Please consider the environment before you print On 16 nov. 2012, at 10:43, Tudor Girba wrote: > Hi, > > Thanks a lot. I now created another package named MethodWrappers42 (instead of MethodWrappers4.2). > > Cheers, > Doru > > > On 15 Nov 2012, at 19:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On Nov 15, 2012, at 2:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >>> Hi, >>> >>> We have a little problem with MethodWrappers. Currently, the package is called MethodWrappers4.2 which completely messes up Monticello in Pharo 1.4. >>> >>> So, we (me and Stef) would like to rename it to MethodWrappers42, but for that we need access to the repository. Marcus, could you provide this access? >>> >> >> I actually don't know what state MW is in... there are multiple ports using multiple strategies. The 42 one is for Squeak, I think. >> >> I added you, after fighting with SqueakSource (Stef I could not find in the list) >> >> Marcus >> >> >> >> >> >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> > > -- > www.tudorgirba.com > > "Don't give to get. Just give." > > > > > > Noury Bouraqadi Ecole des Mines de Douai http://car.mines-douai.fr/noury --

Nov. 19, 2012

[Pharo-project] MongoTalk update

by Nicolas Petton

Hi guys, Lately I worked a bit on the Pharo Mongo driver for SmalltalkHub. I made several changes (in the new version 1.4): The query API changed: - MongoCollection>>query: now takes a 1 arg block, improving the API quite a bit. Queries like: aCollection query: (aCollection query query: { 'foo' -> 'bar'} asDictionary; yourself) Is now written: aCollection query: [ :query | query where: { 'foo' -> 'bar'} ] Sending #asDictionary has also been made optional, the query builder will send #asMongoQuery to the query collection. The MongoQueries package: Version 1.4 comes with a new package MongoQueries, a small DSL allowing us to use traditional blocks instead of dictionaries to perform queries. This is optional and backward compatible. Queries like: aCollection select: { '$or' -> { 'name' -> 'foo'. 'age' -> { '$gt' -> 23 } asDictionary } asDictionary } asDictionary can be expressed: aCollection select: [ :each | (each name = 'foo') | (each age > 23) ] The MongoQueries package should support the entire mongo query language (including nested queries), and comes with unit tests. Nico

Nov. 19, 2012

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

by Pavel Krivanek

On Mon, Nov 19, 2012 at 1:49 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20409 > ----- > > Issue 7000: Cleanup unused code in BitBlt class > http://code.google.com/p/pharo/issues/detail?id=7000 > > Issue 7003: use ProvideAnswerNotification for DummyUIManager requests > http://code.google.com/p/pharo/issues/detail?id=7003 > > Issue 6956: Some Ring tests are dependent on Monticello > http://code.google.com/p/pharo/issues/detail?id=6956 Grrr, the extension methods are still not moved to Ring-Tests-Monticello. Maybe we will need to remove this tests in one update and in the next one to add them to the new package. -- Pavel > > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/UIManager-MarcusDenker.88.diff > http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Monticello-MarcusDenker.8.diff > http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Kernel-MarcusDenker.44.diff > http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Containers-MarcusDenker.9.diff > http://ss3.gemstone.com/ss/Pharo20/Graphics-Primitives-MarcusDenker.96.diff > http://ss3.gemstone.com/ss/Pharo20/Graphics-Display Objects-MarcusDenker.94.diff > -- > Marcus Denker -- http://marcusdenker.de > >

Nov. 19, 2012