- Pharo-dev - lists.pharo.org

[Pharo-project] Create a changeset for an entire package?
by Javier PimÃ¡s Aug. 16, 2009

Aug. 16, 2009

It seems fixing bugs is not the only hard part... I've a bunch of fixes for GLCanvas, and a small proposed change for the class browser but I can't find a way to export a diff of all the changed packages, nor a diff of an entire package nor a diff of a class so anybody can see the changes before commiting... Do I have to file out every class I changed? there has to some easier way. Thanks, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

8 12

[Pharo-project] Spelling error in method name
by csrabak＠bol.com.br Aug. 16, 2009

Aug. 16, 2009

2 1

[Pharo-project] New Pharo based on core 10413
by Damien Cassou Aug. 16, 2009

Aug. 16, 2009

Please download and report problems: http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

4 3

[Pharo-project] Mouse does not find matching when closing paren is immediately following single quotes
by csrabak＠bol.com.br Aug. 16, 2009

Aug. 16, 2009

2 1

[Pharo-project] Newbie new initialize [WAS: Incompatibilities was: #< if at first you dont succeed..]
by Ken.Dickey Aug. 16, 2009

Aug. 16, 2009

I highly recommend _Squeak by Example_. My recollection (highly suspect) is that they refer to the base change which added #initialize. http://squeakbyexample.org/ Good on you, -KenD

2 1

[Pharo-project] Monitoring Transcript progress from UI Process
by Chris Muller Aug. 15, 2009

Aug. 15, 2009

Greetings, I am a Pharo newbie. What a nice image! One of the things I'd like to do is monitor the Magma test-suite while it runs; Magma intercepts Notifications from its test suite code to simply Transcript show: them by default. But the Transcript doesn't render them while the UI process is busy, as the following demonstrates: "Screen doesn't update until entire script is complete.." World findATranscript: nil. 1 to: 100 do: [ : n | Transcript cr; show: n; endEntry ] I also tried a World doOneCycleNow but it blows up.. Doesn't seem right anyway.. Thanks, Chris

2 1

[Pharo-project] #< if at first you dont succeed..
by Ken.Dickey Aug. 15, 2009

Aug. 15, 2009

Igor Stasenko <siguctua(a)gmail.com> > By reading a comment: Â "Not defined on Complex numbers" > i wonder why implementation is different than following: ... How about this wording: "Mathematically, complex numbers are a superset of the real numbers. Complex numbers with a zero imaginary part ARE real numbers and should behave as such. That the #< selector is part of the Complex class is an artifact of the current implementation. There is no agreed upon model for < comparison for complex numbers in general." Better? -KenD

2 1

[Pharo-project] #< if at first you dont succeed..
by Ken.Dickey Aug. 15, 2009

Aug. 15, 2009

> i disagree. > As i said earlier, a square root function result is not defined for > arguments less than zero in real (R) set. Right, only for complex (C). R < C [C contains R]. > This is strictly mathematical behavior, same as division does not > defines a value for zero. My _Elementary Functions_ book has a nice section which defines the square root of -1 to be 1i. I pick up _Handbook of Physical Calculations_ and find an entire section on the mathematics of alternating current which uses complex math exclusively. I see why, given Smalltalk's history, one does not wish to change the way things are done. This is a bit different from implying complex mathematics is not mathematics. > Just think about, how many code i could break, if i return an Infinity > (or something like this) as a result of division by zero instead > of signaling error. My recollection (again, not to be trusted) is that Java returns an IEEE infinity rather than throwing an exception. I do not recommend this either, which is why I am puzzled by #ln returning a NaN. Again, my recommendation is that the current Complex implementation be removed from Pharo-Core. Reluctant as I am to suggest it, an allowComplexResults global preference could be used, with the usual "Here Be Dragons" warnings. Such a preference would clearly state that it is to allow functions like #ln and #sqrt to return complex results and would only be settable if a Complex number package was loaded. Cheers, -KenD PS: My apologies, but my laptop died and I am borrowing time on someone else's computer. I intent to browse "sqrt senders" when I get another machine to see what code is breaking.

4 3

Re: [Pharo-project] #< if at first you dont succeed..
by Ken.Dickey Aug. 15, 2009

Aug. 15, 2009

Taking a hint from the comments (yes, I do listen), here is a "less complex" :) solution: Complex>> < aNumber "Not defined on Complex numbers" ^self asReal < aNumber asReal Complex>> asReal "Answer real-part of self if imaginary is zero else, error" (imaginary = 0) ifTrue: [^real] ifFalse: [self error: 'Can''t convert to real'] Better? -KenD

4 3

[Pharo-project] [ANN] Fundamentals volume 1
by Andres Valloud Aug. 15, 2009

Aug. 15, 2009

Hello, I just published the 400 page book Fundamentals of Smalltalk Programming Technique, volume 1. To some extent it's fitting that I am publishing another book this time of the year. I started writing the Mentoring Course book (of which the Hash book was chapter 7) almost 4 years ago. The three books total about 1200 pages. Something I realized with the Mentoring Course book is that I could take advantage of mentoring myself because I had already sharpened several Smalltalk skills. The Fundamentals book talks about these abilities. As with the Mentoring Course book, there is too much material for a single book. Thus, the first volume just published talks about the controlled manipulation of boolean expressions, inheritance, and polymorphism. In fact, there is a continuum of points of view on the subjects, ranging from the goal of producing very little yet highly maintainable code, to the architecture of highly optimized implementations, as well as valuable compromises in between. In fact, at times, it is possible to avoid sacrificing flexibility for speed, or viceversa. The second volume will talk about enumeration, recursion, weakness, and optimization. I am sure it will be a fun book to write. In the mean time, enjoy volume 1! http://www.lulu.com/content/7451511 http://www.lulu.com/avSmalltalkBooks Andres.

3 4