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

Re: [Pharo-dev] Bug? AdditionalMethodState suddenly stores Associations

by Marcus Denker

On 05 Nov 2013, at 19:48, Max Leske <maxleske(a)gmail.com> wrote: > I discovered that AdditionalMethodState now (sometimes) stores Associations, not only Pragmas and Messages. That seems to work fine so fare but leads to an exception if #analogousCodeTo: is sent to a state which stores an Association. > I think this is the case when the method stored general properties (non-source visible). see propertyValueAt:put: > Can someone please confirm that this is a bug? > I guess the bug is that analogousCodeTo: should handle the properties correctly. I think just ignoring them would be fine, as they are not part of code, but meta. Marcus

Nov. 6, 2013

Re: [Pharo-dev] No decompile string at all, bad idea?

by Marcus Denker

On 05 Nov 2013, at 20:37, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi. From what I understand you removed the old Compiler but yet Opal does not support compiling. Also, #sourceCode was changed etc... > That means that there is no way to see the decompiled string of a method? Yes. > Which means I cannot deploy and image without sources and then browse/debug/inspect/write pharoDebug.log etc because we don't have even the decompile string??? Exactly. But this is just temporary, .sources and .changes will go away in Pharo4 and there will be just a .pharo4 image file. > Serializing compiled methods is not fun either since we cannot decompile it after... > You can embedd the source into the method before serialising. Marcus

Nov. 6, 2013

Re: [Pharo-dev] Deep Into Pharo: PPExpressionParser

by Tudor Girba

Hi, PPExpressionParser is not meant to be subclassed. Read the class comment to see how to use it. PPCompositeParser is meant to be subclassed and it offers a neat mapping between methods and variables to support caching of parsers. Take a look at the subclasses in the Moose image: http://www.moosetechnology.org/download/5.0 If you are at it, in the Moose image, you also get a dedicated browser (World menu / Moose / PetitParser browser) for manipulating subclasses of PPCompositeParser. Cheers, Doru On Tue, Nov 5, 2013 at 10:11 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > After reading the PetitParser chapter, I'm not clear when one would > subclass > PPCompositeParser vs. using PPExpressionParser. What are the tradeoffs / > use > cases? Also, can the book be improved or is that the final version? Thanks. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Deep-Into-Pharo-PPExpressionParser-tp4719454.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 6, 2013

Re: [Pharo-dev] WhatsUp from: 2013-11-04 until: 2013-11-17

by Yanni Chiu

On 04/11/2013 9:42 AM, phil(a)highoctane.be wrote: > > - make use of SandstoneDb + Fuel storage Interesting. Can you share your reasons for choosing these technologies? Why not GemStone? MongoDB? Or, are you still experimenting?

Nov. 6, 2013

NBOpenGL VM crash.

by Ronie Salgado

I'm trying to use the latest version of NBOpenGL in Windows in Pharo 3.0. First I'm receiving a "Not suitable implementation" error message. This can be solved by adding the following at the class side of NBWin32GLContextDriver. NBWin32GLContextDriver>>supportsCurrentPlatform ^ NativeBoost platformId = NativeBoostConstants win32PlatformId Then, trying the following Roassal3D example produces a VM crash: R3Example new city Attached is the crash.dmp file. Currently, we are using an old pharo image for developing Roassal3D under windows. Greetings, Ronie Salgado

Nov. 6, 2013

Re: [Pharo-dev] Latest Xcode to Compile VM

by Sean P. DeNigris

Yes, no compiling during holidays! We don't want you burning out. In fact the no work of any kind... unless it's releasing Mars ;) but still better after holiday... Will you let me know after you've successfully compiled with latest Xcode so I can upgrade. Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Latest-Xcode-to-Compile-VM-tp4719249p4719481.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 6, 2013

Re: [Pharo-dev] Feature request poll

by Paul DeBruicker

For whomever wonders what "what have the romans ever done for us" is about watch: http://www.youtube.com/watch?v=9foi342LXQE you can stop around 2:10 -- View this message in context: http://forum.world.st/Feature-request-poll-tp4718993p4719475.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 6, 2013

Re: [Pharo-dev] Feature request poll

by Eliot Miranda

On Tue, Nov 5, 2013 at 10:01 AM, GOUBIER Thierry <thierry.goubier(a)cea.fr>wrote: > I find this debate interesting... but a bit strange > > For me, Smalltalk-80 is what is inside the 80's book, and no > implementation of Smalltalk was really Smalltalk-80 but something else > (some principles plus a huge amount of code)... Pharo is no more different > from Smalltalk-80 than all the others were, and, compared to Self, Pharo > looks like a very tame variant :) > > So for me, Pharo will stay Pharo Smalltalk: a member of a large family > which I had the pleasure to work in and use for a very long time, and in > many different shapes but still respecting the same core principles. > +1. Saying Pharo is not a Smalltalk is clearly absurd. At the risk of getting into a "what have the romans done for us?" thread, I'll say the following. The syntax is a superset of Smalltalk-80 (additions being literal ByteArrays, pragmas, class messages for creating weak arrays & ephemerons). The class library is a superset of Smalltalk-80 plus bug fixes. The only significant extensions are closures, exceptions and traits, but exceptions and traits, much like Dan Ingall's and Alan Borning's multiple inheritance implementation in Smalltalk-80 is done in the language. Closures are nicer than SMalltalk-80 blocks, but they're the same essential light-weight lambda idea with somewhat improved semantics, and all that was wrong with Smalltalk-80 blocks was the lack of reentrancy. A language like Newspeak is "Smalltalk-inspired". It differs significantly (semantics: nested classes, lexically-scoped outer sends, mixins, syntax: ability to elide self, initialization of temps with their declaration). I don't see the point of saying Pharo is not Smalltalk. I see the point of saying Pharo is not Squeak, and I thoguht that was the point. But saying Pharo is not Smalltalk is petty larceny. > > Thierry > > ________________________________________ > De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Sean P. > DeNigris [sean(a)clipperadams.com] > Date d'envoi : mardi 5 novembre 2013 17:53 > Ã : pharo-dev(a)lists.pharo.org > Objet : Re: [Pharo-dev] Feature request poll > > Tudor Girba-2 wrote > > Pharo is Pharo. And we should promote it like that. > > It is inherently confusing because originally "Smalltalk" meant "a > language/environment that's continually reinvented every 4 years based on > the knowledge gained by the last iteration". Then, Smalltalk-80 was frozen > and released, and "Smalltalk" was repurposed in the wider world as a > shorthand for Smalltalk-80. So, one would be correct in saying that Pharo > is > Smalltalk in the original meaning, as the next iteration after 80 (although > it missed the 4 year target by a bit ha ha). > > But, since the nearly universal understanding of "Smalltalk" is > Smalltalk-80, the "more true" and practical choice is to say that Pharo is > Smalltalk-inspired (i.e. inspired by Smalltalk-80, but clearly not > Smalltalk-80). > > HTH. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Feature-request-poll-tp4718993p4719415.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > -- best, Eliot

Nov. 6, 2013

Re: [Pharo-dev] TextAttribute, TextAction and TextDoIt or TextURL: not working

by phil＠highoctane.be

,Ooooohhh!!!! I guess I'll restart work on that old 1.3-based project of mine :-) Well, well,this opens a lot of doors! (including doc comments with links inside them for clickable cross refs, like we had in squeak) Now, it is going to be used with Tx stuff ? Phil

Nov. 5, 2013

Deep Into Pharo: PPExpressionParser

by Sean P. DeNigris

After reading the PetitParser chapter, I'm not clear when one would subclass PPCompositeParser vs. using PPExpressionParser. What are the tradeoffs / use cases? Also, can the book be improved or is that the final version? Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deep-Into-Pharo-PPExpressionParser-tp4719454.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2013