- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SHA1 changed ??

by Esteban Lorenzano

cool :) this was annoying me too :P On Sep 23, 2013, at 8:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > https://pharo.fogbugz.com/f/cases/11664/SHA1-hashStream-should-return-a-Byt… > > with slice > > On 13 Sep 2013, at 15:38, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Bump. >> >> Max ? >> >> On 30 Aug 2013, at 13:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> On 30 Aug 2013, at 13:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>>> On Aug 30, 2013, at 1:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>>> I'm not aware of such a change... >>>>> this is probably an error/side effect of something else. >>>>> >>>> This is a side effect of the merging of the two nearly identical but duplicated SHA1 implementations in the imageâ¦ >>>> >>>> https://pharo.fogbugz.com/f/cases/5469/SHA1-duplicated-implementations >>> >>> I want to wait for Max to respond/explain. >>> >>> But according to http://en.wikipedia.org/wiki/Sha1 >>> >>> "SHA-1 produces a 160-bit (20-byte) hash value. A SHA-1 hash value is typically expressed as a hexadecimal number, 40 digits long." >>> >>> The previous contract of returning a ByteArray of size 20 is more correct than an Integer, although both are mathematically equivalent. It is also very easy to send #hex to a ByteArray to get the most common human representation of such a hash. >>> >>>>> Esteban >>>>> >>>>> On Aug 29, 2013, at 3:05 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> >>>>>> Max, >>>>>> >>>>>> Why was the contract of SHA1>>hashStream: changed ? >>>>>> >>>>>> It used to return a ByteArray like other HashFunction subclasses, now it returns an Integer. I see that you also changed the tests with this assumption. >>>>>> >>>>>> MD5 hashMessage: 'foo'. >>>>>> >>>>>> #[172 189 24 219 76 194 248 92 237 239 101 79 204 196 164 216] >>>>>> >>>>>> SHA1 hashMessage: 'foo'. >>>>>> >>>>>> 68123873083688143418383284816464454849230703155 >>>>>> >>>>>> It broke Zinc-WebSockets in 3.0 and now I will have to do an ugly hack to make the code work on multiple Pharo versions. >>>>>> >>>>>> Can you please explain ? >>>>>> >>>>>> Sven >>>>> >>>>> >>>> >>> >> > >

Sept. 24, 2013

Re: [Pharo-dev] [NB] Trying to implement a ReadStream on NBExternalAddress

by Luc Fabresse

2013/9/24 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Isn't Eliot just implementing this feature, having a segment of non > relocatable objects? > AFAIU, yes ;-) Cheers, Luc > > > 2013/9/23 Igor Stasenko <siguctua(a)gmail.com> > >> >> >> >> On 23 September 2013 21:40, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> >>> >>> >>> On 23 September 2013 16:23, Camillo Bruni <camillobruni(a)gmail.com>wrote: >>> >>>> Hi Jan, >>>> >>>> I think I will add the ByteArray accessor to NBExternalAddress today >>>> or tomorrow since I need it as well for another project. >>>> >>>> hmm, reading from memory into bytearray can be done with memory copy: >>> >>> inputs: address , offset , size to read >>> >>> newAddress := NBExternalAddress value: address value + offset. >>> buffer := ByteArray new: size. >>> NativeBoost memCopy: newAddress to: buffer size: size. >>> >>> same way, writing, just swap the source and destination: >>> >>> newAddress := NBExternalAddress value: address value + offset. >>> buffer "is given from somewhere". >>> NativeBoost memCopy: buffer to: newAddress size: size. >>> >>> but as Jan noted, you cannot tell to write starting at specified offset >>> from/to bytearray, e.g.: >>> >>> copy from: address to: buffer + someOffset >>> neither: >>> copy from: buffer + someOffset to: someAddress >>> >>> this where we need to introduce special 'field address' type, so you >>> can construct it like this: >>> >>> offsetAddress := buffer nbAddressAt: offset. >>> >>> so then you can use it to pass to any function, which expects address, >>> like memory copy >>> or any foreign function. >>> >>> Since objects are moving in memory, we cannot calculate address of field >>> before hand: >>> >>> address := NBExternalAddress value: someObject address + offset. >>> >>> because if GC will happen, after computing such address and its actual >>> use, >>> you will read/write to wrong location. >>> >> >> ** after computing and *before* actual use ** >> >> >>> Thus we should keep oop + offset up to the point of passing it to >>> external function, under >>> controllable conditions, that guarantee there's no GC is possible. >>> >>> >>> Things would be much simpler if we could have pinning, isnt? :) >> >> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > >

Sept. 24, 2013

Re: [Pharo-dev] [Esug-list] New Mars examples: Package Browser and Test Runner

by Carla F. Griggio

Nope! I should learn how to do that :P I'll try to do it this week. On Tue, Sep 24, 2013 at 9:04 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi Carla, > > this is cool ! Is there a ready Pharo + Mars image built by jenkins server > ? > > Cheers, > > Laurent > > > On Tue, Sep 24, 2013 at 4:42 AM, Carla F. Griggio <carla.griggio(a)gmail.com > > wrote: > >> Hi everyone! >> I want to let you know that I've just posted a screencast in my blog >> about the new Mars Package Browser and Test Runner<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…> >> . >> These examples are not really intended as being the definitive package >> browser or test runner, but to start experiencing how is it to build a real >> application using Mars and to showcase some widgets. Anyway, it's cool :) >> The Package browser is not so different to the system browser example I >> showed before, but the Test Runner is definitely my favorite example so far. >> >> I give more details in the screencast<http://www.youtube.com/watch?v=RlBr42uaqxE>and the blog >> post<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…>. >> Any feedback is appreciated! >> >> Cheers, >> Carla. >> >> _______________________________________________ >> Esug-list mailing list >> Esug-list(a)lists.esug.org >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> >

Sept. 24, 2013

Re: [Pharo-dev] [Esug-list] New Mars examples: Package Browser and Test Runner

by laurent laffont

Hi Carla, this is cool ! Is there a ready Pharo + Mars image built by jenkins server ? Cheers, Laurent On Tue, Sep 24, 2013 at 4:42 AM, Carla F. Griggio <carla.griggio(a)gmail.com>wrote: > Hi everyone! > I want to let you know that I've just posted a screencast in my blog about > the new Mars Package Browser and Test Runner<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…> > . > These examples are not really intended as being the definitive package > browser or test runner, but to start experiencing how is it to build a real > application using Mars and to showcase some widgets. Anyway, it's cool :) > The Package browser is not so different to the system browser example I > showed before, but the Test Runner is definitely my favorite example so far. > > I give more details in the screencast<http://www.youtube.com/watch?v=RlBr42uaqxE>and the blog > post<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…>. > Any feedback is appreciated! > > Cheers, > Carla. > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > >

Sept. 24, 2013

Smalltalkhub - REST API :) (a.k.a. Sorry, if I broke it...^^)

by Marcel Taeumel

Hi! :) I am just trying out a tool thus querying the SmalltalkHub instance at smalltalkhub.com via its REST interface. Unfortunately, it just stopped responding when I tried to fetch all MC file listings in a query. It now gives a 502. Sorry for that. :-/ Best, Marcel P.S.: I only wanted to retrieve this list once having it cached locally. But the query did not finish even once... <http://forum.world.st/file/n4709948/smalltalkhub-browser.png> -- View this message in context: http://forum.world.st/Smalltalkhub-REST-API-a-k-a-Sorry-if-I-broke-it-tp470… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 24, 2013

Pharo Wiki cleanup

by Camillo Bruni

In my attempt to make the contribution process for Pharo a bit simpler I cleaned up the fogbugz wikis which where left a bit unmaintained. There are now 5 important top-level categories: Welcome Page: https://pharo.fogbugz.com/default.asp?W41 Documentation: https://pharo.fogbugz.com/default.asp?W69 Changelog: https://pharo.fogbugz.com/default.asp?W2 Wishlist: https://pharo.fogbugz.com/default.asp?W50 Responsibilities: https://pharo.fogbugz.com/default.asp?W66 I removed old cruft that was documenting long gone features of ancient pharo versions ;). I would be more than happy to get some feedback and improve these websites gradually.

Sept. 24, 2013

New Mars examples: Package Browser and Test Runner

by Carla F. Griggio

Hi everyone! I want to let you know that I've just posted a screencast in my blog about the new Mars Package Browser and Test Runner<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…> . These examples are not really intended as being the definitive package browser or test runner, but to start experiencing how is it to build a real application using Mars and to showcase some widgets. Anyway, it's cool :) The Package browser is not so different to the system browser example I showed before, but the Test Runner is definitely my favorite example so far. I give more details in the screencast<http://www.youtube.com/watch?v=RlBr42uaqxE>and the blog post<http://marsonpharo.wordpress.com/2013/09/24/marspackagebrowser-and-marstest…>. Any feedback is appreciated! Cheers, Carla.

Sept. 24, 2013

Re: [Pharo-dev] 11635: Race condition in SequenceableCollection>>shuffle

by btc＠openinworld.com

Sept. 24, 2013

Re: [Pharo-dev] 11635: Race condition in SequenceableCollection>>shuffle

by btc＠openinworld.com

Sept. 24, 2013

slow RPackageOrganizer >> packageNamed:

by Camillo Bruni

@Esteban what is the reason we have to do a case-ignored check for looking up a package in #packageNamed:? seems unnecessary slow to me :/, maybe we can add a #packageNamedIgoreCase: ?

Sept. 23, 2013