August 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Strange parameter swapping in Pharo's COG extensions

by StÃ©phane Ducasse

thanks nicolas. Stef On Aug 23, 2013, at 10:40 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > This is only for the CogVMSimulator but it looks like parameters were messed up, see the last 2: > > makeDirEntryName: entryName > size: entryNameSize > createDate: createDate > modDate: modifiedDate > isDir: dirFlag > fileSize: posixPermissions > posixPermissions: fileSize

Aug. 23, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Paul DeBruicker

Norbert Hartl wrote > Am 23.08.2013 um 13:21 schrieb Sven Van Caekenberghe < > sven@ > >: > >> Now, this is the normal behaviour, maybe something did change somewhere. > > most likely :) > > Norbert This: RFBServer start. Smalltalk snapshot:true andQuit: false. works fine in Pharo 1.4 on eliots vm ( version 2732) but locks up in the pharo vm. The SIGUSR1 report looks the similar to the one I posted above. Should I just downgrade to Pharo 1.4 if I want RFB? Thanks Paul -- View this message in context: http://forum.world.st/How-do-diagnose-image-locks-up-cpu-100-on-save-tp4704… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 23, 2013

Strange parameter swapping in Pharo's COG extensions

by Nicolas Cellier

This is only for the CogVMSimulator but it looks like parameters were messed up, see the last 2: makeDirEntryName: entryName size: entryNameSize createDate: createDate modDate: modifiedDate isDir: dirFlag fileSize: posixPermissions posixPermissions: fileSize

Aug. 23, 2013

Re: [Pharo-dev] Debugger recursion

by StÃ©phane Ducasse

On Aug 23, 2013, at 7:13 PM, jan.struz <public+pharo(a)struz.cz> wrote: > Proxy implementation did you have a look at Ghost because mariano spent nearly a year on it. I do not really know what are the messages supposed to be supported by ProtoObject to be debugged May be it is not in the contract of ProtoObject and as such it produces normally an infinite loop. Stef >> why do you inherit from protoObject? >> >> Stef >> >> On Aug 23, 2013, at 12:34 PM, jan.struz < > >> public+pharo@ > >> > wrote: >> >>> the code: >>> >>> ProtoObject subclass: #A >>> instanceVariableNames: '' >>> classVariableNames: '' >>> poolDictionaries: '' >>> category: '_Test'. >>> >>> A>>doesNotUnderstand: aMessage >>> self halt. >>> ^ nil >>> >>> A new kiss. >>> >>> >>> >>> ----- >>> Save The World! >>> -- >>> View this message in context: >>> http://forum.world.st/Debugger-recursion-tp4704703p4704751.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> > > > > > > ----- > Save The World! > -- > View this message in context: http://forum.world.st/Debugger-recursion-tp4704703p4704791.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 23, 2013

Re: [Pharo-dev] Debugger recursion

by jan.struz

Proxy implementation StÃ©phane Ducasse wrote > why do you inherit from protoObject? > > Stef > > On Aug 23, 2013, at 12:34 PM, jan.struz < > public+pharo@ > > wrote: > >> the code: >> >> ProtoObject subclass: #A >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: '_Test'. >> >> A>>doesNotUnderstand: aMessage >> self halt. >> ^ nil >> >> A new kiss. >> >> >> >> ----- >> Save The World! >> -- >> View this message in context: >> http://forum.world.st/Debugger-recursion-tp4704703p4704751.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> ----- Save The World! -- View this message in context: http://forum.world.st/Debugger-recursion-tp4704703p4704791.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 23, 2013

Re: [Pharo-dev] Debugger recursion

by StÃ©phane Ducasse

why do you inherit from protoObject? Stef On Aug 23, 2013, at 12:34 PM, jan.struz <public+pharo(a)struz.cz> wrote: > the code: > > ProtoObject subclass: #A > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: '_Test'. > > A>>doesNotUnderstand: aMessage > self halt. > ^ nil > > A new kiss. > > > > ----- > Save The World! > -- > View this message in context: http://forum.world.st/Debugger-recursion-tp4704703p4704751.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 23, 2013

[Off-Topic] Looking for a VisualWorks developer

by Sven Van Caekenberghe

Hi, On behalf of a contact of me, I am posting the following job offer. I am well aware that this is not the correct list, please feel free to distribute this message further. It could be important for someone, and it is always good to have more people making a living doing Smalltalk. Delaware Consulting [ http://www.delawareconsulting.com ] is looking for at least one full stack Cincom VisualWorks Smalltalk developer to help maintain and further evolve a large custom-made ERP solution of a manufacturing company in Belgium. If you are interested, please contact me at sven(a)stfx.eu for a more detailed document describing the project and requirements, as well as more concrete contact details. Thanks, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Aug. 23, 2013

Re: [Pharo-dev] The Pharo Advantage: what is it for you?

by Sven Van Caekenberghe

On 23 Aug 2013, at 10:32, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > Hello, > > As part of the defense of a budget and technology choices, what would you guys list as a key advantage of using Pharo for creating software solutions? > > My current stack is: > > Pharo 2.0 > Seaside 3 (including Seaside-REST) > Magritte 3 > Twitter Bootstrap > > + a couple of data storage stuff (DBXTalk, Phriak, Voyage) > + STOMP > > + Amber if needed > > I've been test driving the whole stack for a while and even if there are some quirks, it looks like good enough for what I want to achieve. > > Now, my question: what is the Pharo advantage you would put forward vs other choices (like LAMP, Java, Rails etc). > > I am aware of what those could be but I am more looking for what makes you tick when using the technology (like: "it is fun to work with", "no more Java for me, due to ...", "speeds dev time by ...", "not NSA-backdoor-enabled") > > This is the kind of thing we should have in stock for helping the Consortium members get buy in from people giving a yes on budgets. > > Thanks in advance for your help! (BTW, I am going to use this on monday morning for defending our position on a significant project). > > Phil A small team with sufficient real world software development experience, domain knowledge and practical Pharo experience can be an order of a magnitude more efficient than a larger team using a traditional approach and classic technology. Pharo is a uniquely dynamic environment that is both very simple and very powerful. It allows its developers to focus on what really matters, without the complexities of other tools, while remaining very flexible. It is one of the few languages that are really object oriented and offer access to readable source code, all the way down. The ecosystem around Pharo is strong enough to be able to deliver already existing solutions as well as the resources to build new solutions to specific problems. It is an environment that attracts individuals that deeply care about doing software development correctly. ;-) Sven

Aug. 23, 2013

Re: [Pharo-dev] [Pharo-users] The Pharo Advantage: what is it for you?

by Esteban A. Maringolo

2013/8/23 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Hello, >> >> As part of the defense of a budget and technology choices, what would you guys list as a key advantage of using Pharo for creating software solutions? > > - Pool of accessible experts > - Pool of other software solution developers > - Full stack access, no need to wait for another release to address a problem. > - Growth of the community > - Consortium > - I saw in one bank using Pharo (not public unfortunately) putting stability of the language I think Phil was referring to the technological/frameworks stack. Sadly, IMHO, almost every item you mention is surpassed by other non-mainstream or "trendy" technologies/stacks (JS, Erlang, Scala and others). One thing that, for me is a key differentiator is: - how easy is to change code on the fly - really complete debugging environment - objects all the way down - Easiness of the syntax (small, compact and homogeneous) Frameworks come and go, but I really like and feel like an advantage (even though the first two are not "Pharo exclusive"): - Seaside REST (pragmas are really convenient way to define it) - Magritte 3 - Zinc I want to take a look into STOMP, but didin't have time yet. I also like Voyage. Regards, Esteban A. Maringolo

Aug. 23, 2013

Re: [Pharo-dev] How do diagnose image locks up (cpu 100%) on save?

by Norbert Hartl

Am 23.08.2013 um 13:21 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Now, this is the normal behaviour, maybe something did change somewhere. most likely :) Norbert

Aug. 23, 2013