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

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Alexandre Bergel

> To me, this raises a more general question. > How can we trace a particular change in Pharo? > Why when and where this change did occur? I know all is in the > Monticello repository, but is there a quick and convenient way to > answer such a question? I mean avoiding a manual scan of each and > every Monticello version... This is an interestion question that I asked myself many times. Here is an idea: - Adding a button 'search' in a Monticello repository inspector (the one you get when opening a repository) - with a 'search' button, you can then enter a method location such as TextMorphEditor>>keystroke: - the list of versions that either added the method or removed it according to the ancestors. How does that sound? I can work on it. Cheers, Alexandre > > > 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Hi folks. I noticed that this two methods were removed from >> ThirtyTwoBitRegister: >> >> asByteArray >> ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: >> -8) with: >> (hi bitAnd: 16rFF) with: (hi bitShift: -8) >> >> >> >> reverseLoadFrom: aByteArray at: index >> "Load my 32-bit value from the four bytes of the given >> ByteArraystarting at the given index. Consider the first byte to >> contain the >> mostsignificant bits of the word (i.e., use big-endian byte >> ordering)." >> >> hi := ((aByteArray at: index + 3) bitShift: 8) + >> ( aByteArray at: >> index + 2). >> low := ((aByteArray at: index + 1) bitShift: 8) + >> ( aByteArray at: >> index). >> >> >> >> I need them for Glorp. I looked but I didn't found a similar >> message for >> them. I don't think adding them as an extension is a good solution >> here >> since this seems to be very "internal". is there a reason of the >> removing? >> If not, could them be added again? If there are reason, which >> should be the >> best approach to fix this in mi case? >> >> I have no problem in commit them if you want. >> >> Thanks! >> >> Mariano >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 19, 2009

Re: [Pharo-project] AlienFFI new package

by Fernando olivero

IA32ABIPlugin ?? NewsqueakIA32ABIPLugi Michael, The entry for the plugin is there, could you change the name to AlienFFI plugin please. The version for MAC OS is 1.1.0. I dont know the versions of the other OS, perhaps Eliot can provide that info. Fernando On May 19, 2009, at 9:42 AM, Torsten Bergmann wrote: >> 1. place the external plugin IA32ABI in the proper folder > > Can you make the plugins for the various platforms available > and send a mail to Michael Rueger (or on the list) > so they get included on http://code.google.com/p/pharo/wiki/VMPluginOverview > > Thx > Torsten > -- > Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + > Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2009

Re: [Pharo-project] System > About is too big for the Pharo screen

by Adrian Lienhard

This is issue http://code.google.com/p/pharo/issues/detail?id=657 There is a fix but it has not been integrated yet. Adrian On May 19, 2009, at 10:21 , Oscar Nierstrasz wrote: > > If your real screen is not big enough, you can never get rid of this > information box. Can it be fixed so it is the right size for the > default Pharo image? > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 19, 2009

[Pharo-project] System > About is too big for the Pharo screen

by Oscar Nierstrasz

If your real screen is not big enough, you can never get rid of this information box. Can it be fixed so it is the right size for the default Pharo image? - on

May 19, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Nicolas Cellier

To me, this raises a more general question. How can we trace a particular change in Pharo? Why when and where this change did occur? I know all is in the Monticello repository, but is there a quick and convenient way to answer such a question? I mean avoiding a manual scan of each and every Monticello version... Or is it logged in the ChangeSet? In this case, what hidden menu or code snippet will help tracking the change? Or should we use the issue tracker? Ideally, the reason for every change should be logged here. And every Monticello uploaded should refer to an issue. Even if this were strictly applied, not sure that is the way to retrieve information at such a detailed level. If none of these tools can provide an easy answer, then yes, requests on mailing lists, IRC, or internet search can provide a much efficient answer. But that's the signature a tool is lacking. I wish Mariano gets an answer, but an answer on the method would be more profitable to every one. Cheers Nicolas 2009/5/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi folks. I noticed that this two methods were removed from > ThirtyTwoBitRegister: > > asByteArray > Â Â Â Â Â Â ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: -8) with: > (hi bitAnd: 16rFF) with: (hi bitShift: -8) > > > > reverseLoadFrom: aByteArray at: index > Â Â Â Â Â Â Â Â "Load my 32-bit value from the four bytes of the given > ByteArraystarting at the given index. Consider the first byte to contain the > mostsignificant bits of the word (i.e., use big-endian byte ordering)." > > Â Â Â Â Â Â Â Â hi := ((aByteArray at: index + 3) bitShift: 8) + ( aByteArray at: > index + 2). > Â Â Â Â Â Â Â Â low := ((aByteArray at: index + 1) bitShift: 8) + ( aByteArray at: > index). > > > > I need them for Glorp. I looked but I didn't found a similar message for > them. I don't think adding them as an extension is a good solution here > since this seems to be very "internal". is there a reason of the removing? > If not, could them be added again? If there are reason, which should be the > best approach to fix this in mi case? > > I have no problem in commit them if you want. > > Thanks! > > Mariano > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

[Pharo-project] AlienFFI new package

by Torsten Bergmann

>1. place the external plugin IA32ABI in the proper folder Can you make the plugins for the various platforms available and send a mail to Michael Rueger (or on the list) so they get included on http://code.google.com/p/pharo/wiki/VMPluginOverview Thx Torsten -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

May 19, 2009

Re: [Pharo-project] MNU Error in Class Browser (Package Browser)

by Alexandr Batalshikov

This patch solve problem with debugger ("invalid utf8 input detected")but not problem with Class Browser. On Mon, May 18, 2009 at 8:13 PM, Dale Henrichs <dale.henrichs(a)gemstone.com>wrote: > Nicolas Cellier posted a workaround ( > http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg08727.ht…) > The workaround is in an attachment at the very end of the message. > > Dale > >

May 19, 2009

Re: [Pharo-project] Understanding of new Eliot Closures

by Hernan Wilkinson

you can find info in his blog: http://www.mirandabanda.org/cogblog/category/cog/ 2009/5/18 Mariano Martinez Peck <marianopeck(a)gmail.com> > Hi! I am trying to make Glorp work on Pharo, and I having some problems. In > squeak I inspect [] and I see I have a BlockContext object. In latest Pharo, > I get a BlockClosure. I guess this is about Eliot changes ? > > Now, Glorp has 5 methods extension in BlockContext. I saw BlockContext and > BlockClosure and they have no hierarchy in common. So, if I want Glorp to > work in squeak and pharo I must copy all that 5 methods from BlockContext to > BlockClosure? is there a better solution ? I tried the first one and seems > to work ok but I don't know if it is correct. > > Thanks in advance, > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 19, 2009

[Pharo-project] Regarding Alien: IA32ABI plugin

by Fernando olivero

Hello John, I need to modify IA32ABI plugin, (the ALIEN plugin), because the specialObjectsArray was modified and its size is now 50 instead of 52, as the plugin assumes. So both methods Alien>>ensureInSpecialObjectsArray and UnsafeAlien>>ensureInSpecialObjectsArray can have the proper index of 51 and 53, instead of the previous 53 and 55. Could you tell me in what part of the plugin i should modify it? so i can build a new one. Thanks! Fernando pd: i'm forwarding this to the list in case anyone else can help!

May 19, 2009

[Pharo-project] AlienFFI new package

by Fernando olivero

Hello, During last SATTOSE together with StÃ©phane and Johan Brichau we worked on Alien FFI. Now it loads again into Pharo. Summary: a. Removed most of the "library" behavior from Alien, so now the libraries are reified: AlienLibrary and its subclasses. b. We moved the examples in Alien class to an AlienExamples class. c. Moved the libC related methods and glu code to the LibCLibrary class ( take a look at the qsort and printf methods). To load Alien framework you should: 1. place the external plugin IA32ABI in the proper folder 2. load the AlienLoader package from the Alien project in squeaksource. 3. Evaluate "AlienLoader loadInPharo " To test that it was succesfuly installed, you can do the following: 1. Evaluate AlienLoader loadLibC 2. Run the test AlienExamplesTest>> testLibCPrintf Any comments, or advice is appreciated. Fernando pd: The main problem with Alien loading into lastes Pharo was that the Alien and UnsafeAlien are added to the specialObjectsArray, and the size of it was modified since Alien package was originally published by John. pd2: Still didn't try out the AlienLoader>>loadWin32, cause i have a mac. Will try to do it in the next week.

May 19, 2009