- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 1.1] #11304

by StÃ©phane Ducasse

Thanks! Stef On Apr 1, 2010, at 1:31 PM, Marcus Denker wrote: > 11304 > ----- > > Issue 2248: Catchall for unsent message removal > Issue 2246: remove KedamaFloatArray > Issue 2233: asSortedArray should be deprecated > Issue 2200: Duplicated code between ChangeSet and ChangesOrganizer > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010

Re: [Pharo-project] Test for Collection>>sorted

by Hilaire Fernandes

StÃ©phane Ducasse a Ã©crit : >>> Hilaire you should read the paper on traits. >> pointer on *one* good tutorial? I think I already read something. A small memento on the syntax to define and to use trait will be enough to get started comfortably. If there are such a things I suggest we add it in good place in the pharo web site (along a paper on unit test); these features are essential parts -- features -- of Pharo, so why not emphasis it. > > this is on my todo for the next book but well other people could help... For now, adding two entries on the FAQ with link to reference material about Trait and Unit Test could help and be helpful. >> Btw, it would be a nice idea to convert an html version of the Pharo by example book, so we can have direct pointer to chapter from the pharo web site. It should be doable with latex2html. In the past I used hyperlatex to produce both nice html and pdf version of DrGeo manual (http://documentation.ofset.org/drgeo/fr/drgenius_51.html) > > I do not have time for that. Depending on how is constructed the latex source it could be tedious or not: if command where use to abstract the latex instruction it will be easier. I have commited in the Inbox tests and fixed for sorted, sorted: methods. Trait are indeed nicely used in the test classes. Hilaire

April 1, 2010

[Pharo-project] [update 1.1] #11304

by Marcus Denker

11304 ----- Issue 2248: Catchall for unsent message removal Issue 2246: remove KedamaFloatArray Issue 2233: asSortedArray should be deprecated Issue 2200: Duplicated code between ChangeSet and ChangesOrganizer -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

[Pharo-project] [update 1.1] #11302

by Marcus Denker

Issue 11302 ========== Issue 2250: SmalltalkImage current undeclared -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 1, 2010

Re: [Pharo-project] squeakToUTF-8 and related?

by Henrik Johansen

http://code.google.com/p/pharo/issues/detail?id=1608 Den 1. apr. 2010 kl. 11.31 skrev Michael Rueger <m.rueger(a)acm.org>: > On 4/1/2010 10:38 AM, StÃ©phane Ducasse wrote: > >> So mike could you summarize the Pharo situation. > > Until someone proves me wrong I would say that Pharo is UTF-8 > clean :-) > > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by Andreas Raab

On 4/1/2010 1:06 AM, Marcus Denker wrote: > So then I was wrong with this analysis... but on the big picture, it is true. And you know it. It was. In the past. But I don't live in the past. I live in the present. And in the present, Squeak has moved on. We're past that. We have a great system, a great community, a great contribution process. If you look at the last eight months we've had more contributions than in the previous five years together, both small and large. We have *serious* momentum. We have Etoys and Croquet/Cobalt moving back to Squeak. We'll be having the *second* release this year in three weeks we may even have a third release this year if the momentum keeps up. In any case we're *way* past the issues you mention. Everyone who wants to help Squeak is welcome to contribute[1]. That includes you and Stef. You have standing invitations to join the Squeak core developers so if you have any interest in Squeak left, you'll pick that invitation up and help make Squeak better. At least that's how I judge if someone really loves Squeak - not whether he says it but whether he *does* something to improve it. [1]http://squeakboard.wordpress.com/2009/07/02/a-new-community-development-m… Cheers, - Andreas

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by Bert Freudenberg

On 01.04.2010, at 10:06, Marcus Denker wrote: > > > On Apr 1, 2010, at 9:43 AM, Andreas Raab wrote: > >> On 4/1/2010 12:12 AM, Marcus Denker wrote: >>> >>> On Apr 1, 2010, at 12:00 AM, Niko Schwarz wrote: >>> >>>> Hi, I just bumped into this. Probably this is intended somehow, but it >>>> does seem weird enough to ask â¦ >>>> >>>> (Object>> #hash) asString class >>>> >>>> returns 'Text'. >>>> >>>> >>> >>> I think this is historical. Methods *used* to return Strings, and the Browser highlighted the first line. >>> >>> Than, when the possibility to have "Rich text" kind of methods (with bold, colors, links) added in Squeak, >>> this was "implemented" by the "do the smallest change possible, we will rewrite everything anyway" strategy. >>> >>> Never clean up! Never Refactor! >> >> Wow, Marcus. Your hostility towards Squeak is seriously amazing. Hey guys, don't ruin the peace just yet, okay? http://xkcd.com/386/ > It's not hostility. Not at all. It's my *love* for Squeak that was/is the problem. I could just not do nothing, *because* > I loved it so much... my mistake. Loving something is never a mistake. >> Even more so since CompiledMethod>>asString DOES NOT EXIST in Squeak. > > So then I was wrong with this analysis... but on the big picture, it is true. And you know it. > > Marcus Yep. Besides, who hasn't been surprised the first time you use #getSourceFromFile returns a Text? Certainly I was. It makes sense since source code for us is of course not just a string, but it's surprising nonetheless. /back to lurking - Bert -

April 1, 2010

Re: [Pharo-project] squeakToUTF-8 and related?

by Michael Rueger

On 4/1/2010 10:38 AM, StÃ©phane Ducasse wrote: > So mike could you summarize the Pharo situation. Until someone proves me wrong I would say that Pharo is UTF-8 clean :-) Michael

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by StÃ©phane Ducasse

yes it is :) I laugth a lot. Stef On Apr 1, 2010, at 10:48 AM, Adrian Lienhard wrote: > Guys, is this a fool's day hoax? ;) > > I think we shouldn't get agitated because of stuff like this. It doesn't matter what origin the code has. We fix it and then its done. That's how we make progress. And it's supposed to be fun too! > > Cheers, > Adrian > > > On Apr 1, 2010, at 10:23 , Marcus Denker wrote: > >> >> On Apr 1, 2010, at 10:18 AM, StÃ©phane Ducasse wrote: >> >>> More seriously it would be nice to have a solution. >>> After may be string and text can share a common interface and the current situation is kind of ok. >>> Does anybody have a larger view on the problem and possible solution? >> >> I think this was all fixed already in 1.1... >> >> (Object>>#halt) asString class --> ByteString. >> >> There is no asText. but #getSource return a Text (for formatted methods, of course) >> >> (Object>>#halt) getSource class >> >> So not too bad. >> >> Marcus >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> 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

April 1, 2010

Re: [Pharo-project] CompiledMethod asString is a text

by Adrian Lienhard

Guys, is this a fool's day hoax? ;) I think we shouldn't get agitated because of stuff like this. It doesn't matter what origin the code has. We fix it and then its done. That's how we make progress. And it's supposed to be fun too! Cheers, Adrian On Apr 1, 2010, at 10:23 , Marcus Denker wrote: > > On Apr 1, 2010, at 10:18 AM, StÃ©phane Ducasse wrote: > >> More seriously it would be nice to have a solution. >> After may be string and text can share a common interface and the current situation is kind of ok. >> Does anybody have a larger view on the problem and possible solution? > > I think this was all fixed already in 1.1... > > (Object>>#halt) asString class --> ByteString. > > There is no asText. but #getSource return a Text (for formatted methods, of course) > > (Object>>#halt) getSource class > > So not too bad. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 1, 2010