June 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] SmaCC
by Ross Boylan Dec. 12, 2010

Dec. 12, 2010

I'm using the Pharo 1.0 image and have loaded the configuration for SmaCC. It doesn't seem to come with any instruction or examples about how to use it, and I seem to have only the SmaCC-Runtime package group. I think I need SmaCCDev, but can't figure out how to load it. I opened up the monticello browser, but when I try to add a repository it asks me for an email address. I would appreciate help on any or all of figuring out how to use SmaCC, loading SmaCCDev (or any other packages) and info about package management in Pharo. Thanks. Ross Boylan

5 10

[Pharo-project] Using Pharo from the command-line
by Stefan Marr Dec. 2, 2010

Dec. 2, 2010

Hello: I just try to get started with Pharo to experiment with some benchmarks and would be grateful for some basic hints, since the documentation on pharo-project.org is not to excessive. As far as I read in the documentation of the language shootout[1], I will need the OSProcess package. How can I load this package into the image downloaded from p-p.org? My second problem is to execute code from the command line. I tried a simple example file $ cat test.sq Transcript open; cr; show: 'Hello, world'. $ Squeak\ 4.2.1beta1U.app/Contents/MacOS/Squeak\ VM\ Opt pharo1.0-10418-BETAdev09.08.3.image test.sq But this only leads to a debugger popping up in installSourceFile saying "No content to install". Looks like aStream is nil which should have the data loaded from file:test.sq Any pointers to documentation which might discusses command line related features are very welcome. I actually just need a way to choose a benchmark to be executed from the commandline. The actual code could already be in the image. Many thanks and best regards Stefan [1] http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=squeak&la… -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525 -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

9 12

[Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by Adrian Kuhn Oct. 23, 2010

Oct. 23, 2010

Hi Pharo list, The lastest akuhn/SUnit runs fasters tests first. When running your test suite for the second time, faster tests are run first. For the whole 9000 tests in the dev image, this means that the first 8000 tests are run in like 10 milliseconds. Also I fixed the menues in the test runner, you can now mark either all or single tests are expected defect. If you mark expected defects through the UI they are stored on the class side. The #expectedFailures method on the instance side is still taken into account for compatibility, but storing expected defects on the class side is the preferred way to do it now. I also cleared up the vocabulary. There are no more history on the class side, rather there are two histories one called "last run" and one called "expected defects" that both serve different purposes. The "last run" history is used to mark test results in the browser. The "expected defects" history is used to keep track of expected / unexpected defects. (As far I know, the icons in O2 show this as well.) Plus I added the ability to step through a failed tests. This stops right before the actual test method, rather than at the failed assertion. To step through a failed test, run your tests with the test runner and use the menu of test failures or errors. (OB and O2 might consider adding this option as well. In particular in combination with running fasters tests first a "run and debug/step-through first failure" might be interesting.) To load akuhn/SUnit gofer SystemChangeNotifier uniqueInstance noMoreNotificationsFor: TestCase. Gofer it disablePackageCache; squeaksource: 'akuhn'; package: 'SUnit'; package: 'SUnitGUI'; load. Thank you all for the awesome feedback last time! More is welcome :) --AA

3 5

[Pharo-project] Autotest / TDD + screencast
by laurent laffont Oct. 14, 2010

Oct. 14, 2010

Hi, Here's a first usable version of Autotest (automatic test runner, inspired by Ruby's ZentTest autotest). The goal is to have instant feedback on the code you The screencast to see it in action: http://lolgzs.free.fr/pharo/autotest_1.mpeg To load it: Gofer new squeaksource: 'Autotest'; package: 'Autotest'; load Comments are welcome as I have to rewrite it better :) Repository is read / write for those who wants to contribute. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

3 3

[Pharo-project] is it possible to know the memory occupation (bytes) of an object?
by Mariano Martinez Peck Sept. 27, 2010

Sept. 27, 2010

Hi. I don't know if "memory occupation" is the better name. I just want to know the amount of memory that an object is occupying in RAM. I mean, the amount of bytes. Is this possible ? if true, how ? I would like to do it from both sides: image and VM. I checked both but I didn't find anything. Thanks in advance Mariano

6 21

[Pharo-project] TextEditor and NewTextMorph merges and fixes
by Fernando olivero Sept. 13, 2010

Sept. 13, 2010

Issue: 2375 Name: System-Text-FernandoOlivero.8 Author: FernandoOlivero Time: 17 May 2010, 3:22:14 pm ###################################### Issue: -- Name: Morphic-FernandoOlivero.588 Author: FernandoOlivero Time: 17 May 2010, 1:42:04 pm

3 9

[Pharo-project] Magma in Pharo 1.1
by Mariano Martinez Peck Sept. 8, 2010

Sept. 8, 2010

Hi. I was trying the welcome workspace of Pharo 1.1 in order to install Magma but it fails. I am evaluating: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load The error was a Sintax Error in lazyX ^ x ifNil: [x _ Period or right bracket expected ->42] I attach screenshot. It seems the problem with the underscore as they are not allowed anymore as asiggment in Pharo 1.1. In order to appear in Pharo welcome workpsace this should be working. If someone makes the changes and updates de configuration please let me know (sorry but I don't have time to do it myself). Otherwise, I will have to remove it from Pharo 1.1 workspace as it doesn't work and makes confusion. Thanks Mariano

4 5

[Pharo-project] [ANN] Hudson for PharoCore
by Marcus Denker Sept. 7, 2010

Sept. 7, 2010

http://rmod.lille.inria.fr/hudson/ Report for 1.1: http://rmod.lille.inria.fr/hudson/job/PharoCore1.1/lastBuild/testReport/ Report for 1.2: http://rmod.lille.inria.fr/hudson/job/PharoCore1.2/lastBuild/testReport/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 2

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]
by laurent laffont Aug. 10, 2010

Aug. 10, 2010

Hi, I've written a proof-of-concept for Autotest. Draft/crappy code and no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta image. Load it: Gofer new squeaksource: 'Autotest'; package: 'Autotest'; load Open it: AutotestView open (there's en entry in WorldMenu > Tools) And change a tested method to see the results. There's a bug I need to find, maybe someone knows: - Change Bag>>occurrencesOf: - Autotest gives: 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 unexpected passes Failures: CollectionRootTest>>#test0FixtureIterateTest Errors: CollectionRootTest>>#testBasicCollect CollectionRootTest>>#testDoWithout but in SUnit CollectionRootTest gives 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes ?? Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > The idea is excellent. > > Cheers, > Alexandre > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > > You may have a lot of noise. > > > > > > I guess that Ruby uses files as a unit of development/deployment. The > closest Smalltalk/Pharo has is the class and the package. > > > > > > I would suggest that TestCase which would use this feature use some > pragma/method to identify/declare which classes/packages this test depends > upon. Then the "autotest" framework would register such tests and listen for > changes in the given classes/packages, launching required tests whenever a > change happen. > > > > > > Additionally, one could declare such a pragma on a single test method, > when this test should be run for a specific class. > > > > > > Of course, you also to take care of long running tests, which you > probably want to exclude from auto-testing. > > > > I see autotest in Pharo in a slighly different way: When I press save in > the Monticello browser, I have a popup menu which asks me whether (i) I want > to run all the tests or (ii) only the tests that cover that I changed from > the last version. > > > > Does this make sense? > > > > Please no popup :) What I like in ruby autotest is that I can quickly > look at test results if I want (or not) without stop writing. Often you want > to see your tests failing, as you type / save code. I don't have to stop > writing, click a button, wait test results, go again.... testing is done in > background and I just see notifications whether it's OK or not. > > > > So test log in a Transcript is OK for me. > > > > > > For autotest unit of work is file: it runs the test file which has the > same name as the code file, but you can customize this behavior. For > autotest-rails: > > "A simplified version of Autotest heuristics in this mode would be: > > When changing a test file, only this file is run (e.g. > test/unit/foo_test.rb âtest/unit/foo_test.rb). > > When changing a model file, only associated unit test file is run > (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > When changing a controller file, associated functional test file is run > (e.g.app/controllers/foo_controller.rb > âtest/functional/foo_controller_test.rb). > > When changing a fixture file, associated unit test and functional test > are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb > +test/functional/foo_controller_test.rb). > > When changing a helper file, associated functional test file is run > (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > When changing application_helper.rb file all functional test files are > run (e.g.application_helper.rb â test/functional/*_test.rb). > > When changing a file under the config directory, all tests are run." > > > > Laurent > > > > > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > 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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

8 51

[Pharo-project] Something I don't see in ImageSegment
by Mariano Martinez Peck Aug. 3, 2010

Aug. 3, 2010

Hi. ImageSegment uses GC to compute the out pointers. Basically, to a given array of roots (a graph) it does: 1) It marks the rootArray and all root objects by turning on the Garbage Collector bit in the object header of those particular objects. 2) Then does a mark pass over all objects. This will stop at our marked roots leaving our segment unmarked in their shadow. 3) Finally, it unmarks the rootArray and all root objects. 4) Only external objects are now marked. The unmarked objects in the graph of objects of the arrays are those who will be put in the WordArray (the segment) and those who are marked to the outPointers. However, I don't see where step 2) is done in Interpreter >> primitiveStoreImageSegment In a piece of such method it does: "Then do a mark pass over all objects. This will stop at our marked roots, thus leaving our segment unmarked in their shadow." savedYoungStart := youngStart. youngStart := self startOfMemory. "process all of memory" "clear the recycled context lists" freeContexts := NilContext. freeLargeContexts := NilContext. self markAndTraceInterpreterOops. "and special objects array" youngStart := savedYoungStart. "Finally unmark the rootArray and all root objects." self longAt: arrayOfRoots put: ((self longAt: arrayOfRoots) bitAnd: AllButMarkBit). ......continue....... But here I see it is only marking Interpreter oops, not all objects. And I don't see where all objects are marked even in the code that follows this little piece. You can see the comment: "Then do a mark pass over all objects" and even without the comment it makes sense to mark all objects in order to detect outPointers. Does anyone has a hint? Thanks Mariano

3 7