- Pharo-dev - lists.pharo.org

[Pharo-project] shout for pharo 1.2: Please help.
by StÃ©phane Ducasse Feb. 28, 2011

Feb. 28, 2011

Hi guys I modified version 1.2.1 of ConfigurationOfShout to load my version Shout-sd.101 (apparently lot of comments were removed between Benjamin.100 and Benjamin.101 - strange) In ConfigurationOfPharo there is project: 'Shout' with: '1.2.1'; Now in ConfigurationOfShout there are version122: spec <version: '1.2.2' imports: #('1.1-baseline')> spec for: #common do: [ spec blessing: #development. spec author: 'Francisco Ortiz PeÃ±aloza'. spec description: 'Shout Changes for 1.2 using new SmalltalkEditor'. ]. version121: spec <version: '1.2.1' imports: #('1.1-baseline')> spec for: #common do: [ spec blessing: #development. spec author: 'Stephane Ducasse'. spec description: 'Shout for 1.2'. ]. When I load the latest stable of Pharo ((Smalltalk globals at: #ConfigurationOfPharo) project version: #stable) load I get an error due to a duplicate (probably the instance variable of pluggableShout.....). Probably loading the wrong package. So I do not know what to do and lost my time. Stef

4 11

[Pharo-project] introducing RPackage :)
by StÃ©phane Ducasse Feb. 28, 2011

Feb. 28, 2011

Hi guys I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. Moose people use it and I will sync with them to know. It would be great if some of you could load and play with the system Gofer new squeaksource: 'PharoInbox'; package: 'ConfigurationOfRPackage'; load. (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. Stef

4 5

[Pharo-project] Which calendar does Pharo officially use?
by DougEdmunds Feb. 28, 2011

Feb. 28, 2011

Try this code in a Workspace: |aDate bDate| Transcript open. aDate := Date fromString: '02.25.2011'. Transcript cr; show: aDate; cr. bDate := aDate subtractDays: 734503. Transcript show: bDate; cr; show: 'Year zero! Which calendar does Pharo officially use?'. >From http://en.wikipedia.org/wiki/0_(year): "Year zero" does not exist in the widely used Gregorian calendar or in its predecessor, the Julian calendar. Under those systems, the year 1 BC is followed by AD 1. However, there is a year zero in astronomical year numbering (where it coincides with the Julian year 1 BC) and in ISO 8601:2004 (where it coincides with the Gregorian year 1 BC) as well as in all Buddhist and Hindu calendars. -- View this message in context: http://forum.world.st/Which-calendar-does-Pharo-officially-use-tp3323638p33… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 1

Re: [Pharo-project] About 1.2
by Marcus Denker Feb. 28, 2011

Feb. 28, 2011

On Feb 27, 2011, at 9:11 AM, laurent laffont wrote: > > > > How can XML in 1.2 impacts 1.1 ??????? > > It's not XML, there is another problem. Status: => 1.2 now builds, without Mocketry. But that has been fixed in the meantime, so we can add it back. (it seems removing is a far better way to get people to fix something than anything else. I will do the same with the MethodWrapper package, you will see how quickly this gets fixed *after* removing it, but never without removing it...) => 1.1 does not build. I don't know why. *first* release 1.2, *than* release 1.1.2... => From the test side of things, there are only two things left in 1.2 -> MethodWrappers has test that fails 50% of the time. This will be solved by removing the package. -> there are Obsoletes after running tests. here I think as this is only after running tests, we can defer to 1.3 and remove the test for obsoletes in 1.2 Besides that, there are a number of things that need to be done for 1.2, they are listed here: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage 1.2 can only be released if this list is empty. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] Gaelli vs. Galli??
by Schwab,Wilhelm K Feb. 28, 2011

Feb. 28, 2011

Are Gaelli and Galli the same person? If so, is there a typo, or is it simply that the name does not translate easily? [5] M. Gaelli, O. Nierstrasz, and S. Ducasse. One-method commands: Linking methods and their tests. In OOPSLA Workshop on Revival of Dynamic Languages. Citeseer, 2004. [6] M. Galli, M. Lanza, O. Nierstrasz, and R. Wuyts. Ordering broken unit tests for focused debugging. In Software Maintenance, 2004. Proceedings. 20th IEEE International Conference on, pages 114â123. IEEE, 2004. Given the identities of the other authors, this seems the easiest place to clarify it :)

3 2

[Pharo-project] Good reference on time on unit testing?
by Schwab,Wilhelm K Feb. 27, 2011

Feb. 27, 2011

Hello all, Can anyone recommend a good reference on the amount of time one should expect to spend writing tests? I will have to be the messenger (will be wearing running shoes just in case...), but I want the message to come from a solid source. Bill

9 22

Re: [Pharo-project] Issue 2820 in pharo: Format Source shortcut key (cmd-r) doesn't work
by pharo＠googlecode.com Feb. 27, 2011

Feb. 27, 2011

Comment #1 on issue 2820 by intrader.intrader: Format Source shortcut key (cmd-r) doesn't work http://code.google.com/p/pharo/issues/detail?id=2820 I have a similar problem what appeared when I loaded Version 1.1.1 of pharo. I have subsequently loaded Pharo 1.2 (Pharo1.2 rc2 Latest update #12335). I have an entry in http://news.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside/23773 that describes the problem. Propblem still remains. P.S. I definitely would not see this kind of problem in eclipse or VS - sad

1 3

[Pharo-project] [COTDC] 20 - Loader
by laurent laffont Feb. 27, 2011

Feb. 27, 2011

Today: Loader 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 Laurent

3 2

[Pharo-project] PharoCasts has a new skin
by laurent laffont Feb. 27, 2011

Feb. 27, 2011

Thanks to Claire & Patrick Barocca, PharoCasts now has its own skin and a nice logo ! http://www.pharocasts.com/ Laurent

1 0

Re: [Pharo-project] 1.2 one-click OSX and Linux: more failing tests
by laurent laffont Feb. 27, 2011

Feb. 27, 2011

1.2 one-click on (Arch) Linux (build #160) there's errors too (see below). So I wonder which VM is used in Hudson ? 10773 run, 10669 passes, 69 expected failures, 6 failures, 29 errors, 0 unexpected passes Failures: FileDirectoryTest>>#testRecursiveMatching ProcessSpecificTest>>#testDynamicVariable FileStreamTest>>#testPositionPastEndIsAtEnd MethodContextTest>>#testClosureRestart BecomeTest>>#testBecomeIdentityHash ProcessSpecificTest>>#testLocalVariable Errors: PharoCorePackageDependenciesTests>>#testMonticello SocketStreamTest>>#testNextIntoClose SocketStreamTest>>#testNextIntoCloseNonSignaling SocketStreamTest>>#testUnCategorizedMethods SocketStreamTest>>#testUnCategorizedMethods SocketStreamTest>>#testUpTo SocketStreamTest>>#testUpTo SocketStreamTest>>#testUpToAfterCloseNonSignaling SocketStreamTest>>#testUpToAfterCloseNonSignaling SocketStreamTest>>#testUpToAfterCloseSignaling SocketStreamTest>>#testUpToAfterCloseSignaling SocketStreamTest>>#testUpToAll SocketStreamTest>>#testUpToAll SocketStreamTest>>#testUpToAllAfterCloseNonSignaling SocketStreamTest>>#testUpToAllAfterCloseNonSignaling SocketStreamTest>>#testUpToAllAfterCloseSignaling SocketStreamTest>>#testUpToAllAfterCloseSignaling SocketStreamTest>>#testUpToAllLimit SocketStreamTest>>#testUpToAllLimit SocketStreamTest>>#testUpToAllTimeout SocketStreamTest>>#testUpToAllTimeout SocketStreamTest>>#testUpToEndClose SocketStreamTest>>#testUpToEndClose SocketStreamTest>>#testUpToEndCloseNonSignaling SocketStreamTest>>#testUpToEndCloseNonSignaling SocketStreamTest>>#testUpToMax SocketStreamTest>>#testUpToMax SocketStreamTest>>#testUpToTimeout SocketStreamTest>>#testUpToTimeout Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ On Sun, Feb 27, 2011 at 6:06 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > I take the last 1.2 one-click on OSX (build #160), run all tests. > > => tests don't finish because > of SocketStreamTest>>#testUpToAfterCloseNonSignaling which wait infinitely > (however, if you run only SocketStreamTests it works). > > So I deselect SocketStreamTests and run again. > > Result: > > 10743 run, 10669 passes, 67 expected failures, 6 failures, 1 errors, 0 > unexpected passes > Failures: > FileStreamTest>>#testPositionPastEndIsAtEnd > MethodContextTest>>#testClosureRestart > ProcessSpecificTest>>#testDynamicVariable > FileDirectoryTest>>#testRecursiveMatching > ProcessSpecificTest>>#testLocalVariable > AllocationTest>>#testOneGigAllocation > > Errors: > PharoCorePackageDependenciesTests>>#testMonticello > > > > Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

1 0