- Pharo-dev - lists.pharo.org

[Pharo-project] float printing
by stephane ducasse Sept. 1, 2010

Sept. 1, 2010

hi guys here is a point where squeak and pharo could sync. Now I propose the change to be applied in Pharo. http://code.google.com/p/pharo/issues/detail?id=2888 in essence 0.1+0.2=0.3 which is normal since (0.1+0.2) hex '3FD3333333333334' 0.3 hex '3FD3333333333333' showing that we are in presence of two difference numbers. So since floats are approximations anyway, I like the idea that the language tells me all the time. This fits perfectly with the discussion and actions we got last year on floats. Of course 0.1s2 + 0.2s2 = 0.3s2 is true storeString is already conveying the right information both in squeak and pharo (0.1+0.2) storeString '0.30000000000000004' 0.3 storeString '0.3' I suggest that printString on float ie on little change in printString. So talk now. My point is that since we cannot perfectly lie better say it. I think that GNU and python are right so this an easy fix with a really good impact on education. Stef printOn: aStream base: base "Handle sign, zero, and NaNs; all other values passed to absPrintOn:base:" self isNaN ifTrue: [aStream nextPutAll: 'NaN'. ^ self]. "check for NaN before sign" self > 0.0 ifTrue: [self absPrintExactlyOn: aStream base: base] ifFalse: [self sign = -1 ifTrue: [aStream nextPutAll: '-']. self = 0.0 ifTrue: [aStream nextPutAll: '0.0'. ^ self] ifFalse: [self negated absPrintOn: aStream base: base]]

1 0

[Pharo-project] Fwd: Pharo1.1 bug report
by StÃ©phane Ducasse Sept. 1, 2010

Sept. 1, 2010

Begin forwarded message: > From: Reza Razavi <razavi(a)acm.org> > Date: September 1, 2010 11:08:30 AM GMT+02:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Pharo1.1 bug report > > Salut Stef, > > Je voudrais te faire part ci-joint d'un rapport gÃ©nÃ©rÃ© par Pharo1.1 [Latest update: #11411], losqu'il rentre dans une boucle infinie (cf. ci-dessous pour les conditions). Je l'ai observÃ© aussi bien sous Linux (Ubuntu) que Windows (Vista). Toutefois, sous Linux, au bout d'une longue attente, la VM m'a affichÃ© un message dont la copie est Ã©galement jointe au format PNG. > > Ceci devrait Ãªtre rÃ©pÃ©table de la maniÃ¨re suivante (j'ai mis du temps avant de trouver) : > - Sauvegarder l'image avec des browsers ouverts > - AprÃ¨s un certain temps, je ne sais en effet pas quelle Ã©tait au juste la durÃ©e d'ouverture des browsers, on passe le curseur sur l'un des deux boutons " Instance " et " Classe ". > > J'espÃ¨re que ceci soit utile, > Bonne continuation, > Reza >

1 0

[Pharo-project] Sockets in Pharo CollaborActive Book
by Sean P. DeNigris Sept. 1, 2010

Sept. 1, 2010

The description of sockets at http://book.pharo-project.org/book/networking/Socket/ is: Socket is one of the main networking classes. You can create a new TCP socket with the message #newTCP. > > This example creates a TCP socket and puts it into listening mode. After a > client has connected, it reads data from the socket. > > | server client | > server := Socket newTCP. > server listenOn: 12345 backlogSize: 4. > server waitForConnectionFor: 600. > client := server accept. > client receiveData > Huh?! It looks like half the code in this snippet belongs on the server, and the other half on the client. I tried: Server doit: server := Socket newTCP. server listenOn: 12345 backlogSize: 4. server waitForConnectionFor: 600. Client doit: server := Socket newTCP. server listenOn: 12345 backlogSize: 4. server waitForConnectionFor: 600. client := server accept. client receiveData. but the server just hung forever. After flopping around for a while, and checking the swiki, it seemed to be listenOn:backlogSize: that was the problem. Everything went well with: Server DoIt: server := Socket newTCP. server listenOn: 8080. server waitForConnectionFor: 600. server sendData: 'Hello from the server' Client PrintIt: client := Socket newTCP. client connectTo: (NetNameResolver localHostAddress) port: 8080. client receiveData. Anyway, I'd like to have this be clearer, but my knowledge is very basic. Also, the class comment for socket reads "...Sockets are the lowest level of networking object in Squeak and are not normally used directly..." so is this where we want to direct people first? Thanks. Sean -- View this message in context: http://forum.world.st/Sockets-in-Pharo-CollaborActive-Book-tp2399361p239936… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

5 6

[Pharo-project] What are you using to write reports?
by Torsten Bergmann Sept. 1, 2010

Sept. 1, 2010

>Well VBA and Excel is well working, I doubt that OpenOffice Basic can >compete with it. Yes, thats why I started to write a COM wrapper for Squeak in 2008 - unfortunately stopped due to missing time and missing callbacks in FFI. And Alien (providing callbacks) is still not available ... Using COM would open the whole windows world (from Office to SAP, ...) and by using CCW' and RCW's one could also use the .NET world. However - there was/is also a Squeak .NET bridge one can use. BTW: Did you look at Javas/Apache FOP? I know it is used by a few Seaside apps to create PDF's using XSL-FO. Bye T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

1 0

[Pharo-project] [update 1.2] #12119
by StÃ©phane Ducasse Sept. 1, 2010

Sept. 1, 2010

12119 ----- - Issue 2889: fix LargeInteger printing. Thanks Levente and Nicolas Cellier. - Issue 2887: Allow ifNotNil: #aSelector. Thanks Henrik Johanssen. - Issue 2886: StrikeFont WideString rendering. Thanks Henrik Johanssen. Stef

1 0

[Pharo-project] Serial ports on Linux
by Schwab,Wilhelm K Sept. 1, 2010

Sept. 1, 2010

I have been able to do serial I/O on Windows, but not Linux. Running in a terminal to capture output yields "Error while saving old state" while trying to open just about any number or name I can think of (including 0 and /dev/ttyS0), but the open method gives no indication that there is a problem; it returns a perfectly valid looking serial port with the #port set to whatever it was given. Subsequent reads fail, and are probably a bit more honest about what is happening: "Error while reading: serial port is not open." I am not sure whether that is always the case, but it certainly is on this machine when I try /dev/ttyUSB0, which does not exist here. Any ideas? Bill

1 0

[Pharo-project] squeaksource seems down...
by StÃ©phane Ducasse Aug. 31, 2010

Aug. 31, 2010

2 1

Aug. 31, 2010

Hi guys We should improve. One way is to make sure that all the tests are green. It will help when integrating fixes. So I need your help. DateAndTimeTest (Sean can you have a look?) and a couple of others need our care. The tests of TimeStamp are red but we should remove this class from the system. Now nothing is simple and I need help here too because MC logic rely on it. Tx! Stef

1 0

Aug. 31, 2010

12118 ----- Redoing from 11217 -------------------------------- - Issue 2880: remove WebClient from pharo. Thanks Andreas Raab. - Issue 2878: enhance MethodDictionaryTests. Thanks Guillermo Polito. Stef

1 0

Aug. 31, 2010

Begin forwarded message: > From: Nicolas Paez <nicopaez(a)gmail.com> > Date: August 31, 2010 5:02:04 PM GMT+02:00 > To: moose-dev(a)iam.unibe.ch, pharo-project-request(a)lists.gforge.inria.fr > Subject: [Moose-dev] [seed] New project around the kernel > Reply-To: Moose-related development <moose-dev(a)iam.unibe.ch> > > Hi, I am working in the RMoD team (INRIA) in a project called Seed. One of the tasks of the project is to identify those mandatory classes that should be part of Pharo kernel. Currently, Pharo kernel has some "unhappy dependecies". We are using Moose + Glamour to create a tool (a browser) that help up with this task. The idea is to start by loading in our browser the classes used in the SpecialObjectsArray and then iterate to add dependencies incrementally. This way we will be able to detect smells and "blacklist" methods we don't want to be part of our kernel. > > During this days we will have a working version of our browser to start the analysis. > If you want to take a look, search for Seed on SqueackSource. > We will be sharing our findings in the Pharo mailing list. > > > > > Regards, > NicoPaez. > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

2 2