- Pharo-dev - lists.pharo.org

[Pharo-project] "Smalltalk signalLowSpace" freeze the image
by Mariano Martinez Peck May 25, 2010

May 25, 2010

Hi. Take Pharo 1.0 or Pharo 1.1. The following code, will probably freeze your image: "Smalltalk signalLowSpace" Can you reproduce it? or I am the only one ? Let me know and I open a ticket. I have tried with all Mac vms. I tried the same in Squeak 4.1 and it works correct. Any idea where it can be the problem? I tried to debug a lot. Of course, it is freezing in "LowSpaceSemaphore signal". I put a halt in #installLowSpaceWatcher and tried to debug #lowSpaceWatcher but I didn't find anything. Thanks for any hint. Mariano

3 2

[Pharo-project] Latex to HelpSystem converter? [WAS] Re: [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1
by Mariano Martinez Peck May 25, 2010

May 25, 2010

On Mon, May 24, 2010 at 11:41 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >We should listen to Torsten but as far as I would expect, only HelpSystem, > >but it is already included in both PharoCore and Squeak. > > The help system is included in Squeak trunk and Pharo core, so > one should be able to load the three example books (Squeak, Pharo, > Metacello) which I uploaded in squeksource/HelpSystem in both > environments. Still they are just small demo books - no real > docu since there is not much content yet. > > However - we could reuse them to document these systems if > for instance Dale is willing to contribute stuff to the > Metacello book or we create an ASCII version of the Metacello > preview PBE chapter. Maybe I am dreaming too much, but it would be cool to export somehow some chapters to HelpSystem. Is there a way to export from Latex to ASCII ? even more, how difficult could be to code a plugin (or whatever name is) to automatically generate the nice code for HelpSystem from Latex code? Then we can include PBE in the image also ;) Cheers Mariano > Would be nice to have a real Metacello help book > that would be part of the Metacello distro (similar to the ProfStef > Tutorial on Metacello) ... > > Thanks > T. > > > > > > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

4 3

[Pharo-project] "Smalltalk signalLowSpace" freeze the image
by Torsten Bergmann May 25, 2010

May 25, 2010

To explain what Gary said: "SmalltalkImage>>lowSpaceWatcher" sends "Project class>>interruptName:preemptedProcess:" which sends "preemptedProcess suspend offList" According to http://code.google.com/p/pharo/issues/detail?id=2276 #offList is obsolete und unnecessary, if you remove the #offList send it should work again. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] What packages to load from Metacello in PharoDev?
by Mariano Martinez Peck May 25, 2010

May 25, 2010

Hi. For building PharoDev images, we take a PharoCore and just evaluate something like: (ConfigurationOfPharo project version: '1.1-beta1.10517') load So....Metacello would be boostraped from ConfigurationOfPharo>>ensureMetacello which does a (Smalltalk at: #ConfigurationOfMetacello) perform: #loadLatestVersion and ConfigurationOfMetacello>>loadLatestVersion does a "self project latestVersion load" ... and, the default of ConfigurationOfMetacello is Core....so, in summary, only core is loaded. Perfect. Now I was thinking that we should load more packages in PharoDev image. First, we want the Metacello tests. For all packages we include by default in PharoDev, we also include its tests (by default). This is cool because people test it, we can give you quick feedback, be sure all green tests, etc. They are cool as documentation, blah blah blah. So, first question, which tests package should I load? Metacello-Tests Metacello-TestsCore Metacello-TestsMC Metacello-TestsPlatform.pharo Metacello-TestsReference Or, maybe even better, load the group 'Test'. I guess this is the correct one. Now, I also think we could include all the following packages: - Tutorial: this is cool for newcomers. They want to do the Metacello tutorial, and having it already in the image is cool I think. I want to include also the tests for the tutorial - HelpSystem for Metacello: we need to copy this package from the HelpSystem repo (see my other email) - Metacello ProfStef - Metacello OB: do you know if it is working in Pharo 1.1 and with OB 1.1.4 ? What do you think about including these packages in PharoDev by default ? I think it is a good idea. Regardless that, I am not sure how to load them. As I told you, when building PharoDev images, Metacello is boostraped from the #ensureMetacello of ConfigurationOfPharo. And this will load the Core. ANd this is correct because other people use COnfigurationOfPharo for their own stuff and they just want the core. But in the case of PharoDev, I want more packages. But modifying #ensureMetacello is not an alternative. So...I can put a reference to ConfigurationOfMetacello in Conf of Pharo, just like any other dependency, and there I specify the loads: with the array of things I want. This seems better. But I still have a problem: #ensureMetacello will load the latestVersion of it. It will load core. So, which version of ConfigurationOfMetacello should I use in my version of ConfigurationOfPharo. If I put a specific version, I may hve problems because it will try to download different versions....So, I would like to load the same as the #ensureMetacello. But I cannot specify in version method lastVersion for metacello. what can I do ? don't specify the metacello version in the version method so that it takes the last one ? Thanks and sorry for the long email Mariano

2 3

[Pharo-project] [GSoC] Coding started yesterday!
by Mariano Martinez Peck May 25, 2010

May 25, 2010

Hi everybody. First, let me apologize for the multiple cross post. I think it is good to show the Smalltalk community periodically the status of GSoC. The good news in this case is that yesterday the students started to code! This was one of the GSoC deadlines that you can read in http://gsoc2010.esug.org/ and in http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#… . Last two weeks or so, students have been talking and discussing with their mentors, reading and investigating about the projects. Some students already started to code before. But yesterday was the official day to start to code. For those that didn't know, we got not 5 but 6 projects. We asked more and they gave us one more ;) Once again, if you want to look at the 6 selected projects, see http://gsoc2010.esug.org/projects We already told students to ask in case of problems or questions to their mentors but also to the community (trough the mailing list). So, let's help them! Students: don't be shy. Ask! ;) Good luck to all students and enjoy this wonderful opportunity you have. Now we are in the best part of the program! Best regards, Mariano Martinez Peck GSoC admin gsoc-admin(a)esug.org http://gsoc2010.esug.org

1 0

[Pharo-project] Monticello keeps "diffing" forvever
by AxiNat May 25, 2010

May 25, 2010

Hi all, A package I had uploaded to monticello was corrupt, and besides -I think it's not relevant, but just in case- squeaksource was down so it was only saved locally. When I realized that the version was corrupt I erased it from the repo, and now every time I try to save a new version it stays "Diffing" forever, should I wait for it to finish (I'm beginning to lose faith in this ever happening) or take a different approach? Thanks! Bernat Romagosa.

1 1

[Pharo-project] How to deal with issue 1594
by Gabriel Cotelli May 25, 2010

May 25, 2010

During the sprint in baires we write some tests to detect the senders of = nil to be replaced with isNil as the issue suggest. We now need to do a rewrite of this methods (this could be done using the refactoring engine as lukas proposed in the issue). However if I do this rewrite on the Dev image I will change code not only in Pharo Core but also in some external packages. Is it the intended scope of the issue?. I think that first we need to do the rewrite on Pharo Core code. And let every package maintainer to decide if he wants to do it or not. Of course for the community maintained packages we can make that decision too. In the future I think would be good to have some kind of "Pharo Coding Practices" (or the name we want) that can be automatically tested. As a community we can discuss this practices and provide some automatic way to ensure that. As soon as posible I will create a Slice with the changes in Pharo Core and post it to the inbox (sorry if it takes me some days but here where are celebrating the argentinean bicentennial so i don't have too much free time this days :) ). Regards, Gabriel

3 2

[Pharo-project] New weak finalization support. Implementation
by Igor Stasenko May 25, 2010

May 25, 2010

Hello, i updated the weak finalization classes. I made its behavior/protocol similar to old WeakRegistry, also all weak registry tests on new class is green. First, file in .st then .cs Also, don't forget about special objects array: http://bugs.squeak.org/view.php?id=7525 And sure thing, you will need a VM support for it. But I am unsure, how to introduce a fallback code (and do we really need it)? I thought, that i could just add a simple startUp routine which does GC to see if new finalization supported by VM. Then it could pick either WeakFinalizationRegistry or old WeakRegistry. But then, it will slow down the image startup significantly, not saying that John fought hard to avoid full memory/heap walk during image startup on iPhone. So, maybe introduce an additional prim into VM, which will tell us if it supports new finalization? Or query the VM version? I need your advice. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] ClassTestCase
by Mariano Abel Coca May 25, 2010

May 25, 2010

Hi, I want to make global the checks included in ClassTestCase, and remove it. That is because actually it's only being tested for it's subclasses. And also, it's declaring that a subclass will be a class test instead of just a test, but no one of it's subclasses actually test the class, but the instances, therefore is a TestCase, not a ClassTestCase. See TimespanTest as an example. What Im saying is that I'm trying to force a run of a suit of Code Standards and Code Quality tests before sending something to merge to a baseline of a project. What do you think? Are you agree with that? Cheers, Mariano.

7 22

[Pharo-project] FFI debugging lesson
by Schwab,Wilhelm K May 24, 2010

May 24, 2010

I did some FFI based work in Pharo 1.0 and realized something that I found surprising; this might help others new to it. An incorrect argument type in a call spec does not result in a compile-time error; instead it leads to "Cannot coerce arguments" at the time of the call. FWIW. Bill

1 0