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

Re: [Pharo-project] Status about compiler _ changes

by StÃ©phane Ducasse

Yes > Folks, > I suggest we follow solution 1 in order to not be stuck. > Then we will add backward compatibility hacks if necessary and if not > too much ugly. > Agree ? > > Nicolas

Nov. 15, 2009

Re: [Pharo-project] Status about compiler _ changes

by StÃ©phane Ducasse

On Nov 14, 2009, at 4:38 PM, Schwab,Wilhelm K wrote: > I feel somewhat responsible for this branch of the thread :( For the record, I am freely willing to "give up" underscore assignment. The idea of allowing it via a whitespace trick seemed worthy of due consideration, but I am liking it less as the debate continues. yes :) This is why discussion is good since common knowledge emerges. > IIRC, the whole mess got started over a desire to have a single keypress for assignment. Sadly, I was not consulted, because that could have been accomplished as an optional feature of the editor (_ inserts :=, backing up over = removes a preceding :, turn it off if you want no part of it; done), but it was instead allowed to seep into the compiler and the sources. > > It can't go away too soon for my tastes, but a transition period makes sense too. Whatever you guys want to do is fine by me. Thanks for tackling the problem!! > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli > Sent: Saturday, November 14, 2009 4:01 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Status about compiler _ changes > >>> (2) it complicates the scanning significantly, the same token >>> represents different things depending on context and an extended >>> lookahead is required to parse it, >> >> I'm afraid I'm not seeing this point. From a brief look at the >> scanner, it appears that allowing := assignment did complicate the >> scanner somewhat, but that allowing _ to mean assignment should be >> similar complexity and still only require one-char lookahead. But >> perhaps I'm missing something. > > You need to make sure that there is a delimiter (or comment) before and after the underscore character, which I think is not trivial to scan. Certainly possible, but not trivial. > > Furthermore it would make it impossible to write code like > > a _ b > > where a is a variable, #_ and #b are unary messages. The above code is valid in other Smalltalk dialects. > >>> and (3) it allows that people >>> continue to use crappy underscore assignments, there will be a mess >>> forever. >> >> I can't (and don't want to) argue with that :-) I'll gladly accept "we >> don't want to allow underscore assignment" as an argument, I'm not so >> sure about the "it's hard" argument. > > I am not saying it is impossible. > > My main concerns are the following: > > 1. I don't like that _ means different things depending on context. > 2. I don't like that the use of _ in identifiers has unnecessary restrictions and exceptions. > 3. I don't want to break compatibility with other Smalltalk dialects. > 4. I don't want to see _ as assignment operator anymore. > 5. I don't want to rewrite the complete compiler, there are probably more changes coming from Eliot for closures, the stack VM and the JIT. > I don't want to make integrating those unnecessarily hard. > 6. I don't want to break irreparably other tools that depend on the Smalltalk syntax like the Refactoring Engine or the NewCompiler. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 15, 2009

[Pharo-project] New Pharo based on core 10495 - Win32 Installer

by Torsten Bergmann

up on the download page -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

Nov. 14, 2009

Re: [Pharo-project] [update 1.1] #11043

by Andreas Wacknitz

Am 14.11.2009 um 20:26 schrieb Marcus Denker: > > On Nov 14, 2009, at 7:16 PM, Andreas Wacknitz wrote: > >> I cannot see updates 11038 and 11039. Neither my own updated image nor this new one show these updates. >> Transcript show: ScriptLoader new logStream contents >> shows that there is a gap in the updates... >> > > Yes, I did two update without the Scriptloader... the changes for speeding up Morphic could only be done without using any > morphic while loading. So I used the same code that gary provided in the bug-tracker entry, with a change of filing in the .cs > from via http instead of a local file. > > The second changeset than had to re-load the dirty packages from the repository and provide a scriptloader with two empty > update scripts. I guess there I should in the future update the log, too. > > Marcus > Thanks for the explanation. Andreas

Nov. 14, 2009

Re: [Pharo-project] No replace menu entry in the tools of Pharo image?

by StÃ©phane Ducasse

> > > I think that having in the menu a find, replace and replace all us VERY useful. Like every single text editor has. > > Does someone know if Zafara has this in mind as a feature? I'm not sure that zafara got continued. We got no news from its father. > I am also agree to have them not only as a shortcut but as a menu entry. > And yes!!!!!!!!! please add an entry to the menu with the shortcuts. I complained about that when this was done. And the answer were that that option was alone in the "help" section. we need code :) > > See the ticket I opened in August: > http://code.google.com/p/pharo/issues/detail?id=1042 > > > Regards, > > -- > Cesar Rabak > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 14, 2009

Re: [Pharo-project] No replace menu entry in the tools of Pharo image?

by Mariano Martinez Peck

On Thu, Nov 12, 2009 at 9:53 PM, <csrabak(a)bol.com.br> wrote: > Em 12/11/2009 19:47, Adrian Lienhard <adi(a)netstyle.ch> escreveu: > > > Hi Cesar > > I don't miss it. How does it work? > > When you select 'replace' instead of 'find' you get a window with > _two_ entry fields one for the string you want to replace and another > for the replacement (OK I concede I'm used to VW ;-) > I think that having in the menu a find, replace and replace all us VERY useful. Like every single text editor has. Does someone know if Zafara has this in mind as a feature? > > > I also wonder where you found the menu item 'set search string'? > > If you click the yellow button in the OB Package Browser in the source > pane you'll find it (Pharo1.0rc1 Latest update: #10495). > > > If there is enough interest from other people we can add the > > replace. But we should take care not to get long menus > > again. Thinking about it, I would remove 'find again (g)' from the > > context menu. Or does anybody use it from the menu, rather than with > > the keyboard shortcut? > > You made an interesting point: for experienced people (who already > learned the keyboard shorcuts) probably the menus are less useful, but > for newcomers or less frequent coders, the menus are the way to > remember the functionality available. So I think if we want to remove > too many items from the menus we have to put back a workspace filled > with an introductory document which among other things has the list of > keyboard shortcuts. Better even would be to have an updated quick > reference card to render in PDF! > > I am also agree to have them not only as a shortcut but as a menu entry. And yes!!!!!!!!! please add an entry to the menu with the shortcuts. I complained about that when this was done. And the answer were that that option was alone in the "help" section. See the ticket I opened in August: http://code.google.com/p/pharo/issues/detail?id=1042 > Regards, > > -- > Cesar Rabak > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 14, 2009

Re: [Pharo-project] annotation pane revival

by StÃ©phane Ducasse

you should publish the slice with the ***other*** mcz in the inbox ? On Nov 14, 2009, at 2:14 PM, Alain Plantec wrote: > Hi all, > For those who like the annotation pane in browsers, changes sorter etc (of Pharo-core) > Here is a SLICE that make it work again. > It also cleans PluggableTextMorph (remove dirty code related to annotation) > Could you check before I send it to the inbox ? > thanks > Alain > <SLICE-annotationRevival-AlainPlantec.1.mcz>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 14, 2009

Re: [Pharo-project] slow method editor on syntax problems

by Mariano Martinez Peck

You should then open a bug ticket! On Fri, Nov 13, 2009 at 1:03 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > > I have not yet investigated the issue but since I guess I must not be > > the only one to see this happen maybe someone has some thoughts or is > > already on the issue (although I could not find an issue on the > > tracker). > > > +1 > You're not the only one > > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;<you._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Nov. 14, 2009

Re: [Pharo-project] [update 1.1] #11043

by Marcus Denker

On Nov 14, 2009, at 7:16 PM, Andreas Wacknitz wrote: > I cannot see updates 11038 and 11039. Neither my own updated image nor this new one show these updates. > Transcript show: ScriptLoader new logStream contents > shows that there is a gap in the updates... > Yes, I did two update without the Scriptloader... the changes for speeding up Morphic could only be done without using any morphic while loading. So I used the same code that gary provided in the bug-tracker entry, with a change of filing in the .cs from via http instead of a local file. The second changeset than had to re-load the dirty packages from the repository and provide a scriptloader with two empty update scripts. I guess there I should in the future update the log, too. Marcus > Andreas > > Am 14.11.2009 um 16:51 schrieb Marcus Denker: > >> 11043 >> ----- >> >> Issue 1441: Add a protection in MCDefinition = >> Issue 1439: Parse should not use typeTable ivar but #typeTableAt: message >> Issue 1440: Monticello packageList speed up >> >> Marcus >> >> >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 14, 2009

Re: [Pharo-project] [update 1.1] #11043

by Andreas Wacknitz

I cannot see updates 11038 and 11039. Neither my own updated image nor this new one show these updates. Transcript show: ScriptLoader new logStream contents shows that there is a gap in the updates... Andreas Am 14.11.2009 um 16:51 schrieb Marcus Denker: > 11043 > ----- > > Issue 1441: Add a protection in MCDefinition = > Issue 1439: Parse should not use typeTable ivar but #typeTableAt: message > Issue 1440: Monticello packageList speed up > > Marcus > > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Nov. 14, 2009