- Pharo-dev - lists.pharo.org

[Pharo-project] failing/errors Pharo Tests with CogVM

by Mariano Martinez Peck

Hi Eliot. I took a Pharo 1.1.1 image (which has included the changes to run Cog) and I run all the tests with the build r2219 And these are the results: 9768 run, 9698 passes, 53 expected failures, 15 failures, 2 errors, 0 unexpected passes Failures: FloatTest>>#testRaisedTo MCInitializationTest>>#testWorkingCopy FloatTest>>#testReciprocal ReleaseTest>>#testUndeclared FloatTest>>#testDivide MethodContextTest>>#testClosureRestart FloatTest>>#testCloseTo FloatTest>>#testHugeIntegerCloseTo FloatTest>>#testInfinityCloseTo WeakRegistryTest>>#testFinalization PCCByLiteralsTest>>#testSwitchPrimCallOffOn AllocationTest>>#testOneGigAllocation FloatTest>>#testNaNCompare FileStreamTest>>#testPositionPastEndIsAtEnd NumberTest>>#testRaisedToIntegerWithFloats Errors: MessageTallyTest>>#testSampling1 WeakSetInspectorTest>>#testSymbolTableM6812 I think that most of these problems were fixed in latest official SqueakVM. I guess they were integrated in VMMaker in versions later than the one you used for Cog. Maybe you can integrate them and create a new version? I am not a VM expert so please if you can help us with this tests it would be cool. Thanks Mariano

Sept. 16, 2010

Re: [Pharo-project] Enable/Disable NewInspector

by Schwab,Wilhelm K

That changes the toolset as a whole (which I have used to good effect, at least in the past), but is there a way to change just the default inspector? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Frederic Pluquet [fpluquet(a)ulb.ac.be] Sent: Thursday, September 16, 2010 10:04 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Enable/Disable NewInspector Execute the following code and chose the toolset you need. ToolSet askForDefault FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet 2010/9/16 Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>> Hi, is there a way to enable and disable NewInspector in a PharoDev image? I don't want to remove neither not load. I want that having both in the system, if there is a way right now to decide which one to use. thanks mariano _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 16, 2010

Re: [Pharo-project] Enable/Disable NewInspector

by Schwab,Wilhelm K

My 1.1 image is showing its age, not because it is aging but because Pharo is evolving. The last time I had to give any thought to it (and I am not a fan of the new inspector), I found that activating the standard toolset gave me most of what I wanted, including using the ordinary inspector instead of the new inspector. However, I just looked at the code I use (aka Migrate) to check, save and load packages, and find that ToolSet default:StandardToolSet. is commented out. It is not immediately obvious whether the image I am using now was built that way, or if (as sometimes happens) I tried a new image, noted that the change was no longer needed and made the change for "next time." If there is a way to keep the new inspector and make it easy to disable, then by all means keep it around. I happen to greatly prefer the explorer for what the new inspector tries to do, but if it is dormant, what's the harm? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Thursday, September 16, 2010 9:26 AM To: Pharo Development Subject: [Pharo-project] Enable/Disable NewInspector Hi, is there a way to enable and disable NewInspector in a PharoDev image? I don't want to remove neither not load. I want that having both in the system, if there is a way right now to decide which one to use. thanks mariano

Sept. 16, 2010

Re: [Pharo-project] Enable/Disable NewInspector

by Frederic Pluquet

Execute the following code and chose the toolset you need. *ToolSet askForDefault* FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet 2010/9/16 Mariano Martinez Peck <marianopeck(a)gmail.com> > Hi, is there a way to enable and disable NewInspector in a PharoDev image? > I don't want to remove neither not load. I want that having both in the > system, if there is a way right now to decide which one to use. > > thanks > > mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 16, 2010

[Pharo-project] Enable/Disable NewInspector

by Mariano Martinez Peck

Hi, is there a way to enable and disable NewInspector in a PharoDev image? I don't want to remove neither not load. I want that having both in the system, if there is a way right now to decide which one to use. thanks mariano

Sept. 16, 2010

[Pharo-project] Best Smalltalk Book of the previous 6 years

by Noury Bouraqadi

Yesterday evening we also announced the result of the survey. And the winner is... Dynamic Web Development with Seaside By StÃ©phane Ducasse, Lukas Renggli, David C. Shaffer, Rick Zaccone, Michael Davies Noury @ ESUG 2010 - Barcelona :-) --- 18th International Smalltalk Joint Conference, September 13 -17 2010 Barcelona, Spain. http://www.esug.org/Conferences/2010

Sept. 16, 2010

[Pharo-project] two dots in latest 1.2 prebuilt image file name

by Pavel Krivanek

Hi, prebuilt PharoCore-1.2-12137 image contanins two dots in the image and changes file name: PharoCore-1.2-12137..image PharoCore-1.2-12137..changes Cheers, -- Pavel

Sept. 16, 2010

Re: [Pharo-project] ProfStef -> latex files?

by laurent laffont

On Thu, Sep 16, 2010 at 9:43 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi! > > There has been an effort to produce latex files from a profstef help? > Never heard about such effort. I've generated a slideshow from it here: http://seaslides.seasidehosting.st/ (works on chrome or safari) and I want to also have a printable document for my course. So I may be interested in latex export too. 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 >

Sept. 16, 2010

Re: [Pharo-project] Another silent failure?

by Schwab,Wilhelm K

Levente, Wasn't it obvious that I thought I found a bug? And yes, there are very long standing "features" that have not been fixed, so it is hardly unprecedented, especially when failure to raise an exception is involved. The Squeak community clearly prefers "fail and ignore" to raising exceptions; they don't see them as defects. Streams and the file system are littered with such problems. The result is a lot of time wasted hunting down things that could have been obvious. However it is of course possible that it could be as you describe, or it could be a common trap. That's why I posted a quick "have you ever seen this behavior?" question to be followed by what you want unless an explanation arises. Not long ago, FFI was raising exceptions indicating that a parameter could not be coerced (or similar language) when the problem was in fact that I was using invalid parameter types in the call sequence. IIRC, Andreas agreed and fixed it, but "lots of FFI users" had apparently not said anything. Absent an explanation of how it would be be problematic, yes, it seems to me that either both byte objects should produce the same behavior, or one of them should raise an exception. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] Sent: Thursday, September 16, 2010 5:57 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Another silent failure? On Wed, 15 Sep 2010, Schwab,Wilhelm K wrote: > Levente, > > FFI, Linux. The point is that the code fails silently when given a string and performs as expected when given a byte array. That is all the more unusual given that the pointer is typed as char* (if anything, I would expect the string to succeed). Just a hunch at this point, it sure looks like something that goes wrong "down in the depths" and it does nothing rather than reporting an error. My question should have been clear (Guillermo obviously got it): does anyone else consider that combination of behaviors to be a problem? Silent failures are the order of the day in Squeak; I hope we will eliminate them in Pharo. So you think that you've found a bug in FFI, but instead of sharing more information about the problem or reporting the bug to the developers, you're blaming FFI and Squeak. There are lots of FFI users who pass Strings to functions which expect char*, and works for them. So, I'm pretty sure that if it's really a bug, then it's specific to the library/VM combination you're trying to use. Levente > > Yes, I can package and release the code. Whether that will take the form of a quick example of what I suspect is a long-standing defect in FFI or a nice wrapper around PLplot will depend on how PLplot performs. > > Windows device contexts are proving difficult to replace. Otherwise, Microsoft can keep the OS. > > Bill > > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] > Sent: Wednesday, September 15, 2010 10:01 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Another silent failure? > > On Wed, 15 Sep 2010, Schwab,Wilhelm K wrote: > >> I am interested in the opinions of helpful people who might have something constructive to add. > > Sorry, but don't expect any help with this attitude. Even the most helpful > people - like Henrik - can't help you, because you don't give enough > information about your problem. > > Which platform do you use? > Which VM/image do you use? > What's the library you'd like to use? > Is #cPlgver: an FFI call or do you use Alien? Maybe something else? > What's the type of the argument it expects? > If it calls a library function, does it store the pointer you're passing > to it? > Can you share your code? > > > Levente > >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Henrik Johansen [henrik.s.johansen(a)veloxit.no] >> Sent: Wednesday, September 15, 2010 6:18 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Another silent failure? >> >> How do you expect us to help you debug this? >> Really? >> >> Cheers, >> Henry >> >> On Sep 15, 2010, at 8:45 38PM, Schwab,Wilhelm K wrote: >> >>> I am playing with a new library and for kicks thought I would call its get-version function: >>> >>> | buffer | >>> buffer := String new:80. >>> PLplotLibrary default cPlgver:buffer. >>> buffer. >>> >>> The above appears to do nothing; the buffer remains blank, and there is no error raised from it. I tried something more complicated involving external address and #alloc: and got the version number. That is encouraging from a perspective of talking to the library, but then I had to square the above failure with my use of memcpy() not long ago (different topic). In that case, I had real need to allocate a buffer in a fixed heap, but was told that I could ultimately copy from said buffer (which lives across multiple gcs and would move) into a ByteArray of the needed size, which would not move during the memcpy() call. That worked. So I tried >>> >>> | buffer | >>> buffer := ByteArray new:80. >>> PLplotLibrary default cPlgver:buffer. >>> buffer asString. >>> >>> and get the version number. What's up? Why is it ok to pass a byte array but not a string? If there really is a difference, there should be an exception hinting that something is wrong and what it might be - right? >>> >>> Bill >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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

Sept. 16, 2010

Re: [Pharo-project] Another silent failure?

by Levente Uzonyi

On Wed, 15 Sep 2010, Schwab,Wilhelm K wrote: > Levente, > > FFI, Linux. The point is that the code fails silently when given a string and performs as expected when given a byte array. That is all the more unusual given that the pointer is typed as char* (if anything, I would expect the string to succeed). Just a hunch at this point, it sure looks like something that goes wrong "down in the depths" and it does nothing rather than reporting an error. My question should have been clear (Guillermo obviously got it): does anyone else consider that combination of behaviors to be a problem? Silent failures are the order of the day in Squeak; I hope we will eliminate them in Pharo. So you think that you've found a bug in FFI, but instead of sharing more information about the problem or reporting the bug to the developers, you're blaming FFI and Squeak. There are lots of FFI users who pass Strings to functions which expect char*, and works for them. So, I'm pretty sure that if it's really a bug, then it's specific to the library/VM combination you're trying to use. Levente > > Yes, I can package and release the code. Whether that will take the form of a quick example of what I suspect is a long-standing defect in FFI or a nice wrapper around PLplot will depend on how PLplot performs. > > Windows device contexts are proving difficult to replace. Otherwise, Microsoft can keep the OS. > > Bill > > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves(a)elte.hu] > Sent: Wednesday, September 15, 2010 10:01 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Another silent failure? > > On Wed, 15 Sep 2010, Schwab,Wilhelm K wrote: > >> I am interested in the opinions of helpful people who might have something constructive to add. > > Sorry, but don't expect any help with this attitude. Even the most helpful > people - like Henrik - can't help you, because you don't give enough > information about your problem. > > Which platform do you use? > Which VM/image do you use? > What's the library you'd like to use? > Is #cPlgver: an FFI call or do you use Alien? Maybe something else? > What's the type of the argument it expects? > If it calls a library function, does it store the pointer you're passing > to it? > Can you share your code? > > > Levente > >> >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Henrik Johansen [henrik.s.johansen(a)veloxit.no] >> Sent: Wednesday, September 15, 2010 6:18 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] Another silent failure? >> >> How do you expect us to help you debug this? >> Really? >> >> Cheers, >> Henry >> >> On Sep 15, 2010, at 8:45 38PM, Schwab,Wilhelm K wrote: >> >>> I am playing with a new library and for kicks thought I would call its get-version function: >>> >>> | buffer | >>> buffer := String new:80. >>> PLplotLibrary default cPlgver:buffer. >>> buffer. >>> >>> The above appears to do nothing; the buffer remains blank, and there is no error raised from it. I tried something more complicated involving external address and #alloc: and got the version number. That is encouraging from a perspective of talking to the library, but then I had to square the above failure with my use of memcpy() not long ago (different topic). In that case, I had real need to allocate a buffer in a fixed heap, but was told that I could ultimately copy from said buffer (which lives across multiple gcs and would move) into a ByteArray of the needed size, which would not move during the memcpy() call. That worked. So I tried >>> >>> | buffer | >>> buffer := ByteArray new:80. >>> PLplotLibrary default cPlgver:buffer. >>> buffer asString. >>> >>> and get the version number. What's up? Why is it ok to pass a byte array but not a string? If there really is a difference, there should be an exception hinting that something is wrong and what it might be - right? >>> >>> Bill >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> _______________________________________________ >> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 16, 2010