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

[Pharo-project] Why CompiledMethod print string shows #identityHah ?
by Mariano Martinez Peck Dec. 6, 2011

Dec. 6, 2011

Hi guys. When printing compiled methods we get something like: TestCase >> #assert: -> (TestCase>>#assert: "a CompiledMethod(585629696)") Where the number is the #identityHash. I have never really needed that, and even more, I always want to print: TestCase >> #assert: -> 'TestCase>>#assert:' So...my question is, is there any reason why it makes so much sense to print the identityHash of a CompiledMethod ? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 2

[Pharo-project] [COTDC] 92 - TSortable
by sean＠clipperadams.com Dec. 6, 2011

Dec. 6, 2011

92 classes done 793 classes remaining Continuing in Collections... Today: TSortable Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

1 0

[Pharo-project] pharo on lion
by Tudor Girba Dec. 6, 2011

Dec. 6, 2011

Hi, Is Pharo working Ok on the new OS X Lion? I am asking because I am considering to upgrade. Cheers, Doru -- www.tudorgirba.com "Not knowing how to do something is not an argument for how it cannot be done."

10 16

[Pharo-project] [update 1.4] #14247
by Marcus Denker Dec. 6, 2011

Dec. 6, 2011

14247 ----- Issue 5062: Proceed Broken http://code.google.com/p/pharo/issues/detail?id=5062 Issue 5060: postscript: do SmalltalkEditor initialize http://code.google.com/p/pharo/issues/detail?id=5060 Issue 4954: MorphicUIManager shall attempt to log the error before opening the UI http://code.google.com/p/pharo/issues/detail?id=4954 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Spock: callbacks and threads
by Schwab,Wilhelm K Dec. 6, 2011

Dec. 6, 2011

Sig, Will Spock have restrictions on which thread invokes a callback? Suppose a library wants to spawn its own thread and invoke a callback from it; would that be possible? As I (partially) understand Eliot's suggestion for making calls on OS threads, the vm would be able to associate each Process with an OS thread; external calls made by a Process would be made on the specified OS thread. That Process, and only that Process, would be blocked during each external call. The first "level" of threaded callbacks that I can envision would be to allow callbacks that come from this associated thread. Does that seem reasonable? It would be great if restrictions are not required, but something tells me they will be necessary. I am being vague in part because I'm over my head here, and because I don't know if the supplier of an evolving library wants to speak yet. The source will be open when they release. Bill

1 0

[Pharo-project] Proceed Broken!
by Sean P. DeNigris Dec. 6, 2011

Dec. 6, 2011

This is a show stopper... http://code.google.com/p/pharo/issues/detail?id=5062 Pharo1.4a Latest update: #14239 - #14246 Clicking Proceed in the Debugger or PreDebugWindow freezes image. Execution is stuck in MorphicUIManager>>terminateUIProcess, which has a 12/2/2011 timestamp. -- View this message in context: http://forum.world.st/Proceed-Broken-tp4163311p4163311.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] [Pharo-users] [COTDC] 90 - TextAlignment
by laurent laffont Dec. 5, 2011

Dec. 5, 2011

On Thu, Dec 1, 2011 at 2:05 PM, <sean(a)clipperadams.com> wrote: > Continuing in Collections... > > Today: TextAlignment > > I'm a Text attribute that tells how content should be aligned. TextMorph new newContents: (Text streamContents: [:aStream| aStream nextPutAll: 'Left flush' asText; cr; nextPutAll: ('Centered' asText addAttribute: TextAlignment centered); cr; nextPutAll: ('Right flush' asText addAttribute: TextAlignment rightFlush); cr ]); openInWindowLabeled: 'TextAlignment demo' Laurent > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > p.s. this message was sent from a pharo image. Did you know you could > easily do that?! > >

2 1

[Pharo-project] [COTDC] 93 - AnnouncementSpy
by sean＠clipperadams.com Dec. 5, 2011

Dec. 5, 2011

Collections is fully commented* Can you believe that!? * Actually, that's a (small) lie. There are a few uncommented classes, but they may be removed pending an open issue, so we'll move on. 92 classes done 14 categories done 795 classes remaining Continuing in Announcements... Today: AnnouncementSpy Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

1 0

Dec. 5, 2011

Hi guys I encourage you to send article to Smalltalk Directions Stef 19thâ21st March 2012, Biloxi, Mississippi Smalltalk Directions is a refereed symposium that will be co-located with the Smalltalk Industry Conference (STIC) in March 2012. The Smalltalk Directions Symposium will run in parallel with STIC, offering a parallel track of presentations of refereed academic work that will be open to all attendees of STIC. We solicit research papers concerned with the future of the Smalltalk language, forward-looking applications of Smalltalk and Smalltalk-inspired languages, and the core technologies supporting such languages, including but not limited to: 1. Libraries & Frameworks 2. Language extensions and contractions 3. Implementation technologies, such as Virtual machines, compilers, instruction sets, garbage collection 4. Object persistence 5. Distributed objects 6. Program development tools and environments 7. Using Smalltalk to educate future object-oriented programmers 8. Design Patterns in and for Smalltalk 9. Modelling 10. Meta-programming 11. Domain-specific languages implemented in Smalltalk 12. Smalltalk on the web Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm; this site also contains links to useful information on how to write effective submissions. We are working to have accepted papers appear in the ACM Digital library. A special issue of the Journal of Object Technology will be published in conjunction with the symposium. The authors of selected papers will be invited to submit an extended version of their Smalltalk Directions submission to this special issue, which will then conduct its own reviewing precess. Papers must be submitted electronically using EasyChair (https://www.easychair.org/conferences/?conf=smalltalkdirections2) Important Dates Paper submission deadline 6th January 2012 Author notification 4th February 2012 Final version deadline 24th February 2012 Symposium 19thâ 21st March 2012 Organizing Committee Andrew P Black Portland State University, USA black(a)cs.pdx.edu Ralph Johnson University of Illinois, Urbana-Champaign, USA rjohnson(a)illinois.edu Roger Whitney San Diego State University whitney(a)cs.sdsu.edu David West New Mexico Highlands University dmwest(a)nmhu.edu

1 0

Re: [Pharo-project] [Pharo-users] [pharo-users] Can't Load Magma in Pharo 1.3
by Mariano Martinez Peck Dec. 5, 2011

Dec. 5, 2011

On Mon, Dec 5, 2011 at 8:22 AM, jtuchel <jtuchel(a)objektfabrik.de> wrote: > Hi Mariano, > > thanks a lot for your tip. So it seems like method > ConfigurationOfMaClientServer>>#version13: needs to be updated. It loads > V4.4.0 of OSProcess. > > spec > project: 'MaBase' with: '1.0'; > project: 'OSProcess' with: '4.4.0'. > > So there is the next question: A look at ConfigurationOfOSProcess reveals > that version440 loads package OSProcess-dtl.59 , as of today, the latest > version on squeak source is OSProcess-dtl.66.mcz. > > How can I find out which one between 59 and 66 is the right one? Or maybe I > Only their developers know. > shouldn't worry about it, but look at ConfigurationOfOSProcess instead... > But searching for ConfigurationOfOSProcess on Squeaksource doesn't bring up > any results. The problem is so well know that we should find a name for it..... it is simple: the guys who do the project, do not do/maintain the Metacello configurations. > So should I be using the MonticelloBrowser to look at > MetacelloRepository? > > Yes, you can. > I tried it on http:://www.squeaksource.com/MetacelloRepository and > surprisingly found out that I have the very latest version of > ConfigurationOfOSProcess loaded: ConfigurationOfOSProcess-mt.17 > > So it seems both ConfigurationOfOSProcess and > ConfigurationOfMagmaClientServer (and therefor I guess all dependent > configurations) need an update... > > Welcome to the real world: nobody updates the configurations. Not even when the load doesn't work. In the case of Magma and OSProcess nor of their developers did/maintain the configurations. I am not saying they shuld. everybody do as much as they can/want, I am just explaining you why it has not been updated. > Coming from Envy I find this whole Metacello stuff both a big improvement > over Monticello and a bit low level. But maybe the last one is just a > question of re-educating myself ;-) > >From my point of view, the problem is not the tool, but how people use it. > Still I am a bit puzzled about what I could do to make Magma load cleanly > into Pharo 1.3, other than fixing that one line in the debugger on every > load. Being an envy user, seeing a debugger during load leaves a bit of a > bitter taste in my throat, because chances are you are going to face > problems that stem from the broken atomicity of a load... > yes... > > But most of all: thanks for the pointers. I have learned a bit more about > Metacello today, which is a good thing! > Read the chapter if you want to know more about the tool itself :) > > Joachim > > > > -- > View this message in context: > http://forum.world.st/Re-Pharo-users-pharo-users-Can-t-Load-Magma-in-Pharo-… > Sent from the Magma mailing list archive at Nabble.com. > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma > -- Mariano http://marianopeck.wordpress.com

1 0