- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [update 1.1] #11252
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: March 7, 2010 6:51:30 PM GMT+01:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [update 1.1] #11252 > > > 11252 > ----- > > - Issue 2118: Let Unicode leadingChar = 0 > Part 3: get rid of (stopConditions at: EndOfRun) (or CrossedX) > Replace with a proper message (stopConditions endOfRun) (crossedX) > > Also: > - Reduce the number of FreeType-overrides, move back to Graphics/Multilingual. > I will republish FreeType later because I don t know if MC will not remove essential methods. > - Do not test alignment == Justified ! > Justified is a Number, alignment = Justified is just so cleaner. > - Prepare TextStopConditions clean-up > > Soon final part >

1 0

[Pharo-project] [update 1.1] #11244
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

- remove the default password squeak in the MCHttpRepository creation template - Introduction of tests for validating the different use cases of Shadowing in CompilerTest. - Improvement in the Encoder>>bindTemp: method in order to make explicit the decisions Thanks Jorge and lukas :)

1 1

[Pharo-project] Fwd: [update 1.1] #11251
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: March 7, 2010 4:47:03 PM GMT+01:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [update 1.1] #11251 > > 11251 > ----- > > - Issue 2119: Complete ensure blocks. Tx Andreas > - Issue 2118: Let Unicode leadingChar = 0 (part 2) > > Stef

1 0

[Pharo-project] Fwd: [update 1.1] #11250
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Date: March 7, 2010 1:34:57 PM GMT+01:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: [update 1.1] #11250 > > 11250 > ----- > > - Issue 2121: Rewrite Binary Selectors Immeditely Followed By Negative Literal. > rewrite all expressions of the form 1@-2 to 1 @ -2, where @ is a binary selector and -2 an negative literal that will soon be parsed as 1 @- (2) (according to ANSI) > > Thanks lukas!!!!! > > Stef

1 0

[Pharo-project] [update 1.1] #11249
by stephane ducasse March 8, 2010

March 8, 2010

11249 ----- - Issue 2114: Enhance SqNumberParser error handling inside Compiler. Tx nicolas - Issue 2116: Compiler sometimes return nil rather than diagnosing the problem. Tx nicolas - Issue 2118: 1) Let unicode leading Char be zero (only 2 methods). Arbitrarily solve the Russian/Nepalese environment conflict. -- SOMEONE HAS TO CHECK WHAT SHOULD THE POLICY BE... -- (I guess a non issue except for OLPC Etoys) 2) Prepare a TextStopConditions object for handling endOfRun/crossedX without breaking a macron. 3) After loading, you should execute: EncodedCharSets initialize. Thanks nicolas Stef

2 1

[Pharo-project] Fwd: [squeak-dev] Re: [smalltalk-research] Re: [Esug-list] Google Summer Of Code 2010 news!!!
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

> Thanks thanks thanks thanks for a refresh on that! > Thanks! > > Stef > > On Mar 8, 2010, at 5:55 PM, Randal L. Schwartz wrote: > >>>>>>> "Randal" == Randal L Schwartz <merlyn(a)stonehenge.com> writes: >> >> Randal> And I believe some heavyweights (with actual lawyers they paid) have >> Randal> already weighed in that the LGPL is equivalent to the *GPL* in a >> Randal> Smalltalk context, so unless the code is explicitly dual-licensed with >> Randal> a more permissive license as well, it taints the entire distro. >> >> Here's the reference: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-January/124027.… >> >> -- >> Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 >> <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> >> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. >> See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion >> > > > >

1 0

[Pharo-project] [update 1.1] #11243
by StÃ©phane Ducasse March 8, 2010

March 8, 2010

11243 ----- - Issue 2102: Fix the fact that local temp can shadow silently instance var --- fixed Problem fixed: We cannot have twice the same block arg in a method [:each | each ...] [:each | each ...] THANKS jorge :) Do you like good bio beer? Stef

6 22

Re: [Pharo-project] XML Parser / Pastell
by Alexandre Bergel March 8, 2010

March 8, 2010

Note that this email is sent to the Pharo mailing list. It is actually more appropriate since the moose mailing list members are also part of Pharo. > I have an update I will push in a day or two that extends namespace > support to attributes and also preserves the order of attributes. > Additionally, the tokenizer has been sped up somewhat. I have also > renamed some of the SAX handlers, but if you have a subclass that > implements them, they will still be invoked but with a warning that > they have been deprecated. Using deprecation is good > I am going back on using Symbols to identify elements and > attributes. The performance of such a Symbol-based system is quite > erratic; running benchmark1 several times (at a much higher > interval), I repeatedly got results in the ~5800 to ~6200 range in a > clean image with XML-Support loaded into it from Monticello. Saving > the image and running it again, I got results in the range of ~4400 > to ~4700. There seems to be a performance hit associated with using > symbols in this fashion that does not abate until you save the image > at least once. Even then my tests seem to indicate that a String- > based system would be slightly faster. This is probably due to the > initial overhead of interning Symbols and the subsequent overhead of > looking them up. Really strange. What make you think it is related to Symbol? Cheers, Alexandre > > ---- On Thu, 04 Mar 2010 12:35:39 -0800 Alexandre Bergel <alexandre(a)bergel.eu > > wrote ---- > >> Hi, >> >> I exchanged a number of emails with Jaayer and Norbert regarding some >> improvements of XMLSupport and its port to Gemstone. >> It may be a bit difficult for people to follow this, but I think it >> is >> important to not discuss privately. >> >>>>>>> I already changed >>>>>>> >>>>>>> XMLTokenizer>>nextName >>>>>>> .... >>>>>>> ^ self fastStreamStringContents: nameBuffer >>>>>>> >>>>>>> to >>>>>>> >>>>>>> XMLTokenizer>>nextName >>>>>>> .... >>>>>>> ^ (self fastStreamStringContents: nameBuffer) asSymbol >>>>>>> >>>>>>> in the gemstone parser to be more consistent. >>>>>> >>>>>> Have you noticed any slow down for this? >>>>>> >>>>> No I didn't do any tests. But if internally all names are symbols >>>>> than I guess converting it while reading is the best way to do. >>>> >>>> I added benchmark1 in XMLParserTest. Really simple way to measure >>>> progress (or slowdown). >>>> On my machine, I have: >>>> XMLParserTest new benchmark1 >>>> => 2097 >>>> >>>> Adding "(self fastStreamStringContents: nameBuffer) asSymbol" >>>> increase the bench to 2273 >>>> >>> I don't believe this ;) you read them as string from the stream. If >>> they are managed as symbols somehow they need to be converted. If >>> not at this place then on some other. I would suspect that there are >>> doubled calls to asSymbol. Could you check the sources? >> >> There is indeed a slowdown. I am not sure where it comes from >> however. >> Executing twice "XMLParserTest new benchmark1" does not return the >> same result. Actually, it increases at each execution! I thought that >> a garbage collect before running the bench would help, does >> apparently >> it does not. >> >> Calling asSymbol on a symbol should not be perceptible I believe. >> >> Cheers, >> Alexandre >> >> >>>>> anElement attributes class (I wrote species but that will fail in >>>>> gemstone too I guess. Hell!) >>>> >>>> I just committed with species. Let me know. This is easy to adjust. >>>> >>> Ok. >>> >>>>>>> The gemstone XML Parser decides somehow to use >>>>>>> IdentityDictionary internally. I think this should be allowed. I >>>>>>> just changed Dictionary to IdentityDictionary so the = test >>>>>>> reflects the right type. If you change it it is clear that it >>>>>>> fails. Because pharo uses Dictionary internally. So you might >>>>>>> see that it is not a question of using Dictionary or >>>>>>> IdentityDictionary but a question of the wrongness of using = >>>>>> >>>>>> How the XMLNodeTest should look like to accommodate your >>>>>> situation? >>>>>> >>>>> I need to recheck this. The problem is really that the XML Parser >>>>> creatios instances of class Association but { #key->'value' } >>>>> creates an instance of class SymbolAssociation. That means I would >>>>> know how to fix the test but I want to understand the implications >>>>> of all of this. I'll get to you if I know anything new. >>>> >>>> Ok. >>>> >>> My mail to the gemstone list led to a ticket about removing class >>> checks from Association. That would be easing the handling a lot. >>> >>> Norbert >>>>> >>>>> >>>>>> Alexandre >>>>>> >>>>>>> >>>>>>>>> Here there is an assumption about the allAttributes collection >>>>>>>>> while using = as comparsion. But there is also an assumption >>>>>>>>> about the order of the content. I changed this to >>>>>>>>> >>>>>>>>> self assert: (firstPerson allAttributes includesAllOf: >>>>>>>>> #(#'first-name' #'employee-number' #'family-name')). >>>>>>>>> self assert: (firstPerson allAttributeAssociations asArray >>>>>>>>> includesAllOf: {(#'first-name'->'Bob'). (#'employee-number'- >>>>>>>>>> 'A0000'). (#'family-name'->'Gates')}). >>>>>>>> >>>>>>>> Very right. My mistake. But wouldn't an asSortedCollection do >>>>>>>> the thing? Do you not test the size of the array. >>>>>>>> >>>>>>>>> This is not the best way to do because the check is only in >>>>>>>>> one direction but for this test it is ok. Somehow the second >>>>>>>>> assert fails and I have to check what is going on here. >>>>>>>> >>>>>>>> Yeah, my mistake. Sorry. The elements may be differently >>>>>>>> ordered. Would a asSortedCollection help? >>>>>>>> >>>>>>>> I have now granted you an access to the repository. You should >>>>>>>> be able to directly commit in it. >>>>>>>> >>>>>>>> Jaayer, what is your Squeaksource account? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Alexandre >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On 28.02.2010, at 02:01, Alexandre Bergel wrote: >>>>>>>>> >>>>>>>>>>> thanks for now. I did a first merge attempt. It will be >>>>>>>>>>> quite a bit of work. For me the xml parser is an important >>>>>>>>>>> component. With the newest changes it became biased towards >>>>>>>>>>> pharo. There are things like ClassTestCase, Unicode >>>>>>>>>>> CharacterSet. These are for sure improvements/changes in >>>>>>>>>>> pharo you like to use. But they make porting a lot more >>>>>>>>>>> difficult. I would be glad if we could find some way to >>>>>>>>>>> lower the porting barrier. The necessary class I could put >>>>>>>>>>> in the squeak compat package in gemstone. But then the xml >>>>>>>>>>> parser will depend on the squeak package which I don't like. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hi Norbert, >>>>>>>>>> >>>>>>>>>> XMLParser effectively depends on Squeak specific classes. I >>>>>>>>>> wrote a small script that identify the squeak classes used in >>>>>>>>>> XML-Support. Here is the list: LanguageEnvironment, Unicode, >>>>>>>>>> LocaleID, CharacterSet >>>>>>>>>> >>>>>>>>>> I guess that porting the whole multilingual support may not >>>>>>>>>> be that easy. The tag xml:lang is used to select the proper >>>>>>>>>> support. It should be easy for you to ignore it I guess. >>>>>>>>>> >>>>>>>>>> CharacterSet seems to be one that has to be ported. It is not >>>>>>>>>> a big class. It depends on WideCharacterSet. I am not sure >>>>>>>>>> whether this is useful in your case however. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Alexandre >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>>>>>> Alexandre Bergel http://www.bergel.eu >>>>>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>>>> Alexandre Bergel http://www.bergel.eu >>>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Re: [Pharo-project] [squeak-dev] Re: [smalltalk-research] Re: [Esug-list] Google Summer Of Code 2010 news!!!
by merlyn＠stonehenge.com March 8, 2010

March 8, 2010

>>>>> "Yanni" == Yanni Chiu <yanni(a)rogers.com> writes: Yanni> GLORP is LGPL, with a subsequently added explanation of how the the Yanni> license should be interpreted in a Smalltalk context. INAL, but this Yanni> still seems muddy, since it's unclear whether or not the author's Yanni> interpretation and intentions would override the actual license, which Yanni> is LGPL. Or, is it the case that the actual license is LGPL + author Yanni> addendums - gah, another license mess. And I believe some heavyweights (with actual lawyers they paid) have already weighed in that the LGPL is equivalent to the *GPL* in a Smalltalk context, so unless the code is explicitly dual-licensed with a more permissive license as well, it taints the entire distro. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

1 1

[Pharo-project] Keyboard shortcuts cheatsheet
by fstephany March 6, 2010

March 6, 2010

Hi there, I've made a small cheatsheet based on an email from Mariano (http://n4.nabble.com/Regarding-the-shortcuts-td1298842.html#a1298842) http://tulipemoutarde.be/documents/pharo_cheat_sheet.pdf I've removed those that were not working or not relevant. Some are still weird though (are cmd+K or cmd+G actually used by someone ?) If you have any suggestions/critics or want to add your favorite shorcut to the list, just let me know. Cheers, Francois -- View this message in context: http://n4.nabble.com/Keyboard-shortcuts-cheatsheet-tp1583170p1583170.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1