- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Changesets with LF/CRLF instead of CR?
by StÃ©phane Ducasse Dec. 1, 2010

Dec. 1, 2010

ok stefan as a general principle, I'm open to change for the better :) Now how much? - cost to do - cost of impact - who is helping to fix bugs after - is community happy? For lot of changes we (me myself and I and a couple of others) take the cost and assume the risks. Now you see my question arriving? Are you in charge, committed (SCRUM reference to the pig and chicken story) ? Stef > Hi Eliot: > > On 29 Nov 2010, at 23:31, Eliot Miranda wrote: > >> Is there an easy way to have change sets filed out with LF instead of the horribly incompatible CR? >> >> Are conversion scipts of help? I depend on the following: > Turns out, an error that lead me to believe there are problems with LF changesets had another cause. (a missing line end at the end of the file) > > So, now I guess, the only thing to do to avoiding the CR line endings in change sets is to convince you guys that CR is not the standard line ending on OS X, and completely outdated in general. > > I would like to suggest to change the behavior of the line-end guessing in MultiByteFileStream to that end. > > Thanks > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

4 5

[Pharo-project] [ANN] New Smalltalk VM Beginners mailing list
by Mariano Martinez Peck Dec. 1, 2010

Dec. 1, 2010

Hi everybody. We want to announce that we've created a mailing list called "Smalltalk VM Beginners" where all the people interested in VM can share knowledge. The aim of this mailing list is create a good and positive energy and spread the knowledge around the Squeak VM. If you always wanted to know something on the VM but never dare to ask, join the mailing-list, may be we will not know it but we will try hard to learn it together. The idea is that we can help each other, welcome people to learn about the VM, and increase and share the knowledge about it in the community. Everybody can ask questions, everybody can help. This mailing list has more or less the same idea of pharo-users or squeak-beginners. Now, to clarify the objectives of the mailing list, we propose some requirements: - Be polite, respectful. - No question is stupid and all questions are welcome. We welcome the most basic questions someone can ask about the VM like, "is it written in C?" "How can I download the code?" - This mailing list should be useful for people that are just interested in knowing a little about the VM, to those who want to know how certain things are done, and specially for those that are learning about the VM because they need to extend or modify it. - If you have a heavy question, you will probably not get the answer in this mailing-list but this is not a problem you can ask in the Squeak VM mailing list. - The idea is that we can help each other. So, the link to the mailing list is: http://lists.squeakfoundation.org/mailman/listinfo/vm-beginners Address: vm-beginners(a)lists.squeakfoundation.org. Cheers

1 0

[Pharo-project] [OSProcess] Proposal for Pharo 1.2 compatibility
by Cyrille Delaunay Dec. 1, 2010

Dec. 1, 2010

Hello, I would suggest to replace the two methods -------------------------------------------------------------- OSPRocess class >> platformName "After Squeak version 3.6, #platformName was moved to SmalltalkImage " ^ ((Smalltalk classNamed: 'SmalltalkImage') ifNil: [^ Smalltalk platformName]) current platformName OSPRocess class >> osVersion "After Squeak version 3.6, #osVersion was moved to SmalltalkImage " ^ ((Smalltalk classNamed: 'SmalltalkImage') ifNil: [^ Smalltalk osVersion]) current osVersion -------------------------------------------------------------- by: ------------------------------------------------------------- OSProcess class >> platformName ^ ((Smalltalk classNamed: 'OSPlatform') ifNil: [ (Smalltalk classNamed: 'SmalltalkImage') current ifNil: [^ Smalltalk platformName]]) platformName OSProcess class >> osVersion ^ ((Smalltalk classNamed: 'OSPlatform') ifNil: [ (Smalltalk classNamed: 'SmalltalkImage') current ifNil: [^ Smalltalk osVersion]]) osVersion ------------------------------------------------------------ to avoid deprecation messages when using it in Pharo 1.2. Does it looks good? I'm not able to publish on the squeaksource repository

4 7

Re: [Pharo-project] Transforming WSDL in a local model - Which HTTP client ? (was Web Services - SoapOpera problems)
by mkobetic＠gmail.com Dec. 1, 2010

Dec. 1, 2010

"Philippe Marschall"<philippe.marschall(a)netcetera.ch> wrote: > Yes, SOAP it not just some XML format. You have to sink a lot of > resources into the implementation and tool support. Keep in mind that > even Cincom with all their resources didn't manage to make their SOAP > library talk to SAP. They had to build a proprietary connector. That's not quite what happened, the SAP Connect relies on the WS stack to do the WS part, it adds SAP specific integration, and yes it also provides the alternative proprietary RFC protocol as well (not everything in SAP was exposed via WS at that point). Anyway, I can certainly sympathise with the sentiment expressed in this thread. IMO, CORBA comes out as the pinacle of simplicity when compared to the WS stack as it is today. The problem is not just the sheer number of specs, but also the laxity and vagueness of individual specs themselves. There's so much room for different interpretations of everything that interoperability beyond trivial examples is nearly impossible (generally the small monkeys just have to ape what the few gorillas decide to do). Anyway, the easiest in this case likely is to simply observe the communication of the PHP based solution and implement just that specific protocol. Each WSDL spec basically defines (whatever that means in the WS context) a custom protocol, you need just one of those, not all of them.

1 0

[Pharo-project] Protocol Buffers anyone?
by GÃ¶ran Krampe Dec. 1, 2010

Dec. 1, 2010

Hi! I want to build an API for Riak (awesome NoSQL db) and there is a choice of using HTTP or Protocol Buffers. Evidently Protocol Buffers offer a quite higher degree of performance so I am leaning towards that. Now, has anyone dabbled with implementing Protocol Buffers for Squeak/Pharo/Smalltalk? Couldn't find anything. regards, GÃ¶ran

1 0

Re: [Pharo-project] Squeaksource down
by Marcus Denker Dec. 1, 2010

Dec. 1, 2010

On Dec 1, 2010, at 8:16 AM, Alexander LazareviÄ wrote: > http://downforeveryoneorjustme.com/www.squeaksource.com It's up again. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Squeaksource down
by Alexander LazareviÄ Dec. 1, 2010

Dec. 1, 2010

http://downforeveryoneorjustme.com/www.squeaksource.com

1 0

[Pharo-project] Ideas for CompiledMethod proxies?
by Mariano Martinez Peck Nov. 30, 2010

Nov. 30, 2010

Hi. I am developing kind of proxies for unused compiled methods. I want to detect them, put a proxy instead of them, and swap them to disk. Then, in case they are used, I put back the original ones. With this, I want to realease memory. This is why I need the proxy objects to be as small as possibles. Right now, I do something like this: aProxy := CompiledMethodProxyReferenceStreamWithFileName installOn: ClassWith1Var selector: #foo. this will instantiate the proxy, do the ClassWith1Var methodAt: #foo put: proxy, write the original compiledMethod that was in #foo into a file, etc.... and then if I do "ClassWith1Var new foo", then using the #run:with:in I load the file from disk and I put back the original method. To know WHICH file I have to load, I have to store the fileName in the proxy object. In addition, if I DON'T execute the compiled method, but instead I send a message, for example: (ClassWith1Var >> #foo) literals this has to do the same: load and put back the original compiled method. To do this, I use the doesNotUnderstand:. This is easy to do if I store the fileName in the proxy instance. Right now, I am using as fileName this: CLASS >> SELECTOR. For example, in this case, the file would be named "ClassWith1Var >> #foo" Now.....with this solution, I need create an proxy instance for each compiled method, and these instances have also another instance for the filename. If I could use the same proxy instance for everybody, the amount of memory released would be muuuuch more. So I thought that maybe from the context I can "guess" the filename if I use conventions. For example, if you do "ClassWith1Var new foo" then in the #run:with:in I receive all the information to KNOW that the fileName should be "ClassWith1Var >> #foo". So, no problem here. But for the second case, suppose "(ClassWith1Var >> #foo) literals", I don't see a way to know this. In this case, #literals is intercepted by the doesNotUnderstand: of my proxy, and here I should load back the original compiled method from disk. The problem is that I cannot know in which CLASS and SELECTOR this proxy was put. The only way I know to do this, is to store the class + selector in the proxy instance....but it is the same...I will need an instance per compiled method. In such case is even easier to directly store the fileName. Anyway, if someone has a solution or advice on this, I would be appreciated that. I tried with thisContext, but it didn't help me. Thanks Mariano

4 23

[Pharo-project] Problem with #garbageCollect and -memory parameter
by Mariano Martinez Peck Nov. 30, 2010

Nov. 30, 2010

Hi folks. I am using the standard SqueakVM 4.2.5beta1U. If I run normaly the VM with a normal Pharo image and I print Smalltalk garbageCollect -> I get something like 492130460 Now...if I run the vm with the parameter -memory 1500m and I then print Smalltalk garbageCollect -> I get a NEGATIVE number like: -619402660 I guess there is a problem in somewhere like ObjectMemory >> bytesLeft: but I don't know... Anyway, the problem in my case is in SmalltalkImage: okayToProceedEvenIfSpaceIsLow "Return true if either there is enough memory to do so safely or if the user gives permission after being given fair warning." self garbageCollectMost > self lowSpaceThreshold ifTrue: [^ true]. "quick" self garbageCollect > self lowSpaceThreshold ifTrue: [^ true]. "work harder" ^ self confirm: 'WARNING: There is not enough space to start the low space watcher. If you proceed, you will not be warned again, and the system may run out of memory and crash. If you do proceed, you can start the low space notifier when more space becomes available simply by opening and then closing a debugger (e.g., by hitting Cmd-period.) Do you want to proceed?' Since both of the first answers false because, of course garbageCollectMost and garbageCollect are negative.... then I have that poup all the time. To fix this I have to posibilities: 1) Just patch this particular method to: self garbageCollectMost. self primBytesLeft > self lowSpaceThreshold ifTrue: [^ true]. "quick" self garbageCollect self primBytesLeft > self lowSpaceThreshold ifTrue: [^ true]. "work harder" Notice that primBytesLeft is answering correct. Wait..I don't know if correct, but at least possitive: 5691396 I think this is possitive because the primitive is not receiving a parameter, and thus, Interpreter >> primitiveBytesLeft evaluates the first part of the method, which just does self sizeOfFree: freeBlock , and not the second part where it does self bytesLeft: aBool. 2) understand why it is negative and fix it from the VM side (I have no idea how to do this). Now, in addition, I wonder if there may be other places broken because of this....I am having some crashed and I don't know why :( Thanks in advance, Mariano

2 2

[Pharo-project] Mocketry in Pharo
by laurent laffont Nov. 30, 2010

Nov. 30, 2010

Hi, Is it OK to add Mocketry in Pharo (Dev) 1.2 ? Should I update ConfigurationOfPharo now ? Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

1 0