September 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50343 Home: https://github.com/pharo-project/pharo-core

Sept. 27, 2015

Re: [Pharo-dev] [Reflectivity] Slides ESUG talk

by Marcus Denker

> On 24 Sep 2015, at 09:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 22 Sep 2015, at 17:23, roberto.minelli(a)usi.ch wrote: >> >> Hi Marcus, >> >> I am finally playing with Reflectivity. In the first place, thanks a lot for this contribution! >> >> I am wondering what is the âcorrectâ way to âremoveâ a MetaLink. Is it enough to call #uninstall on the MetaLink or should I also recompile the class/method where the link is installed? >> >> I spotted a problem with the control #after. If you try to pass #arguments to the meta, an error is returned. To reproduce: http://ws.stfx.eu/ONC4K9KQRTNQ >> >> Is this behavior somewhat desired, or is a bug? >> > Hello, I fixed it: > > https://pharo.fogbugz.com/f/cases/16629/fix-after-on-method-with-arguments > > ... > > I will integrate this fix and then write more tests (e.g. I think there are still problems with an #after on a method that defines temps, > but it will be easy to fix). > As suspectedâ¦ I added a test + fix in 50343. This update contains the #availableReifications method, too. Marcus

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Peter UhnÃ¡k

> > Because to me git is **really** complex. I do not talk about add push > commit but rebase remote.... > Git allows you to do complex things if you need them. But you can easily use git without ever needing rebase, filter-branch or whatnot. Everything that Monticello can do can be done with git easily (commit, push, pull, merge). It just gives you much more powerful tools.

Sept. 27, 2015

Re: [Pharo-dev] Lost in Git...

by Esteban Lorenzano

Hi, yes we need to clarify how it should work :) Esteban > On 27 Sep 2015, at 14:08, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 27/09/2015 13:58, stepharo a Ã©crit : >> Hi guys >> >> I'm totally lost in git/pharo support. >> The only thing I got is that we do not need metacello versions just >> baselines. > > Yes. Metacello on git delegates branches to a repository url mechanism resolution (and desactivate the cache) so just baselines are needed (with a few restrictions because of the way a baseline can include another baseline). > > Makes handling large projects a breeze compared to configurations. > >> We have fileTree, TreeMerge, gitFileTree + tons of git expressions. >> Just looking at the discussion between alex and thierry looks totally >> scary. > > ;) Far less scary than adding a self halt in RBParser these days. > >> Do we have one document explaining the situation clearly? > > I think my presentation from PharoDays is still up to date. Nothing has changed yet. > > I'm still in the dark about libcgit support / plans... > > Note that, from the outside, large projects such as Roassal and Moose use a lot of their energy in solving configurations and merge issues which are linked to the type of repository they use. They also require a significant investment in support tools such as Versionner to get things working. > > Thierry > >

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Esteban Lorenzano

Hi, Iâve been using git for all my projects since more than one year now, and frankly I found it really goodâ¦ and the pull request mechanism is unbeatable. Now, what I do believe is that we need to improve a couple of things: 1) filtree format is not good while working on teams (which is the power of git, after all). Merging is a pain and the merge driver provided by Thierry is just a patch, not a real alternative. 2) double commit is annoying. We have a decent solution for (2), gitfiletree but is not working fine in windows (and thatâs mandatory). I would like a community push here to make it work fine. Once is working, I would like to replace the OSProcess usage with actual libgit2. As far as I understand, this is already possible but we hadnât commit time to make it possible (and I would put it as a secondary goal: first make it work with what we have, then use the library). Now the filetree format has problems merging because it stores some metadata that we do not really need. The origin of this is the fact that is using git as âjust another interchangeable repository for monticelloâ. IMHO while this was desirable for start, is not a good solution now. We do not need that information at all. I worked in a replacement for filetree and as a file format it works fineâ¦ is just a variation who does not stores the not-needed information and relies on STON to manage the one we actually need. After, we can build the actual tools we need. But with that working we will see a lot clearer what we actually need to do :) So I would do a âcall for pushingâ and ask community to spend some time making it work properly. cheers, Esteban > On 27 Sep 2015, at 13:43, stepharo <stepharo(a)free.fr> wrote: > > Alex do you know git? > Because to me git is **really** complex. I do not talk about add push commit but rebase remote.... > Did you try to use sourcetree (the UI for git) to understand what I mean? > So we cannot use git simply we have to propose a much nicer model on top of this assembly. > > Now you can systematicall save your code with monticello and automatically publish it to git. > Esteban has a script for doing that. > > Stef > >> â¦ Pharo may be within the 30 most popular languages on Earth. >> The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. >> >> I wish we had a nice Git integration. >> >> Alexandre > >

Sept. 27, 2015

Re: [Pharo-dev] [review needed] speed up RBClassNotReferencedRule

by Nicolai Hess

2015-08-26 10:25 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > Hi, > > Review needed for > > > https://pharo.fogbugz.com/f/cases/16074/Is-RBClassNotReferencedRule-200x-sl… > > Speedup can be checked with: > > rule:=RBClassNotReferencedRule new. > environment:=RBBrowserEnvironment new forPackageNames: #('Fuel'). > [RBSmalllintChecker runRule: rule onEnvironment: > environment] timeToRun > > > Pharo5: "0:00:00:13.526" > Pharo5 with fix: "0:00:00:00.761" > Pharo3: 0:00:00:00.547 > > Checking all classes for usage: > > [Smalltalk allClassesAndTraits select: [ : each | each isUsed not]] > timeToRun > > still takes 1:40 to find 600 unused classes. > > This shows that adding a cache for âreferenced classesâ per environment > would speed this > up further. But it should be general, not just for RB or even RB Code > Critique. > > The nice things is that code environments only change when you add classes > or methods, > so adding a very general cache should be quite possible. > > Another thing we should add is a way for classes to define âI am usedâ. > E.g this > now finds all Configurations, all the Manifests and all cases like the RB > Rules themselves. > All these should know that they are not useless even though there are no > references. > > Marcus > But now, we have the problem that this rule does not find references to classes by symbol. The comment for this rule says: "This smell arises when a class is not referenced either directly or indirectly by a symbol." But all spec adapter classes are only referenced by their symbol and this now isn't found anymore: MorphicMenuGroupAdapter isUsed " - > false "

Sept. 27, 2015

Re: [Pharo-dev] Lost in Git...

by Thierry Goubier

Le 27/09/2015 13:58, stepharo a Ã©crit : > Hi guys > > I'm totally lost in git/pharo support. > The only thing I got is that we do not need metacello versions just > baselines. Yes. Metacello on git delegates branches to a repository url mechanism resolution (and desactivate the cache) so just baselines are needed (with a few restrictions because of the way a baseline can include another baseline). Makes handling large projects a breeze compared to configurations. > We have fileTree, TreeMerge, gitFileTree + tons of git expressions. > Just looking at the discussion between alex and thierry looks totally > scary. ;) Far less scary than adding a self halt in RBParser these days. > Do we have one document explaining the situation clearly? I think my presentation from PharoDays is still up to date. Nothing has changed yet. I'm still in the dark about libcgit support / plans... Note that, from the outside, large projects such as Roassal and Moose use a lot of their energy in solving configurations and merge issues which are linked to the type of repository they use. They also require a significant investment in support tools such as Versionner to get things working. Thierry

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by stepharo

Coming back from africa I can say that windows is first then linux..... and may be 1% mac >>> we have more than a nice Git integration. I have been using Github for >>> my pharo project for over a year now without any issue, the last few >>> months I have been using gitfiltree which is making it even easier. >>> Definitely beats the alternatives . >>> >> >> Hi! >> >> Did you try to use git on a big project with a team? Did you try to >> merge .st files ? >> I heard it's really annoying to merge files with meta informations on >> git. > >> An other point is that git file tree will not work on Windows if we do >> not fix the problem of the stdio. And a lot of people out of the >> community use Windows, so this is not a issue we should forget. Most of >> the people I know in company use Windows, so if we want to attract >> people this problem need to be corrected. > > I'd really like people who put Windows as an important platform invest > on making sure what we have for Windows support in Pharo really works. > > Thierry > >

Sept. 27, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by stepharo

We should update Garage :) Stef Le 2/9/15 13:35, Sven Van Caekenberghe a Ã©crit : > But Timestamp was already removed completely from 4.0, why re-add it, even deprecated ? > > I am sure many external packages are already modified, I know I did it for mine. > >> On 02 Sep 2015, at 13:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >>> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi guille >>> >>> there is not stress. I just wanted to let you know. >>> I was wondering if just subclassing DateAndTime would not be enough for now. >> Yes, as far as I remember Timestamp was just an empy subclass. >> >> We could: >> >> -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package >> -> Write a Quality Check rule. >> >>> I will go back to code with Pharo 40 >>> >>> stef >>> >>> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>>> If somebody can check it and fix it it would be good :). I've just started my new job and my evenings are busy looking for an apartment or staying in a hostel without a proper internet connection... >>>> >>>> If not, I think we can wait a bit. The first step should be enabling CI jobs for pharo5. Also, I do not think the intersection between 'people using garage opendbx' and 'people using pharo5' is that big to justify a rush. >>>> >>>> Guille >>>> >>>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo <stepharo(a)free.fr> escribiÃ³: >>>> for your info... >>>> >>>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>>> >>>> Stef >>>> > >

Sept. 27, 2015

Re: [Pharo-dev] how do I get the git commit diff

by stepharo

I would like to see the code changed in email. In github first I have to go there (does not work when I'm off) or when internet is slow. Then I have to click/expand and I just want to see the three lines that changes there and there. It works well for the VM mailing-list. In a glance I can see the changes. Without any extra tools. Le 5/9/15 18:43, Dimitris Chloupis a Ã©crit : > the mail is not made for version control, github is. Why you would > prefer a static way of doing things, from a very dynamic website ? > > When you commit to a github repo everyone that watches that repo , > that is everyone that is either a contributor to that repo or a github > user that has clicked the watch button will be alerted about > everything related to that repo. The alerts appear in the front page > of github.com <http://github.com> when you log in. That includes > commits, pull requests, new branches, issues, bugs, feature requests > you name it. You could link that feed to your email so you get email > alerts but personally I prefer keeping my email seperate from version > controlling stuff. > > The advantages of github are too numerous to go in detail here, just > read the github documentation. But to be put short, its easy to link > towards other commits, you can comment commits , you can even comment > specific lines of code (even using markdown ), and edit and commit on > the fly using the website without opening pharo or git pulling to your > local repo. Personally I would prefer to see a lot more pull requests > because they are a very nice way to chain commits together and view > them as one entity since they will concern the same matter. Pull > requests also can be chained to issues and bug reports to mark the > closed or open. > > What you list you refer to ? The link > https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a…, > refers to a single commit with a ton of renamed files. You mean how > you can get the list with the diff of each file changed ? thats easy, > click on the commit. If you go to the repo for example here > https://github.com/pharo-project/pharo-core/commits/4.0 clicking .... > will expand the commit message but you if click on the commit itself > will send you to the list of the diff log for that commit. Do you mean > something else ? > > > > On Sat, Sep 5, 2015 at 10:02 AM stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > I still think that I would like in the squeak mailing-list to see the > diff of every commit by mail. > How can we enable that? Marcus you complain that not enough people are > active but we do not engage people by showing > changes. oh yes they can - by reading git commit.... oh boy if we > believe that people systematically have a look at that then > we are pretty naive. > > Now do not tell me that I can browse git commit I know it and this is > not what I need. > I need SYSTEMATIC awareness of a change. I NEED everybody to be > able to > have look before deleting a mail. > It is working in Squeak. I can in my mail look at the changes. > > Or of course nobody cares in Pharo about changes and we can get > regression. > > Another question: how can I get the list of links to git with the > commit > logs like > https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a… > below? > How can I get the list? so that I can browse (I'm probably one of the > two few interested in fixing bugs after they got introduced). > > > Branch: refs/heads/5.0 Home: > https://github.com/pharo-project/pharo-core > Commit: 8a1f79b44b14f8eafaf6d91a8bab3c28e673114c > https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a… > > Author: Jenkins Build Server <board(a)pharo-project.org > <mailto:board@pharo-project.org>> Date: 2015-09-04 > (Fri, 04 Sep 2015) >

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Thierry Goubier

Le 27/09/2015 13:12, Ferlicot D. Cyril a Ã©crit : > Le 27/09/2015 12:11, Dimitris Chloupis a Ã©crit : >> we have more than a nice Git integration. I have been using Github for >> my pharo project for over a year now without any issue, the last few >> months I have been using gitfiltree which is making it even easier. >> Definitely beats the alternatives . >> > > Hi! > > Did you try to use git on a big project with a team? Did you try to > merge .st files ? > I heard it's really annoying to merge files with meta informations on git. > An other point is that git file tree will not work on Windows if we do > not fix the problem of the stdio. And a lot of people out of the > community use Windows, so this is not a issue we should forget. Most of > the people I know in company use Windows, so if we want to attract > people this problem need to be corrected. I'd really like people who put Windows as an important platform invest on making sure what we have for Windows support in Pharo really works. Thierry

Sept. 27, 2015

Lost in Git...

by stepharo

Hi guys I'm totally lost in git/pharo support. The only thing I got is that we do not need metacello versions just baselines. We have fileTree, TreeMerge, gitFileTree + tons of git expressions. Just looking at the discussion between alex and thierry looks totally scary. Do we have one document explaining the situation clearly? Stef

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by stepharo

Alex do you know git? Because to me git is **really** complex. I do not talk about add push commit but rebase remote.... Did you try to use sourcetree (the UI for git) to understand what I mean? So we cannot use git simply we have to propose a much nicer model on top of this assembly. Now you can systematicall save your code with monticello and automatically publish it to git. Esteban has a script for doing that. Stef > â¦ Pharo may be within the 30 most popular languages on Earth. > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > I wish we had a nice Git integration. > > Alexandre

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Ferlicot D. Cyril

Le 27/09/2015 12:11, Dimitris Chloupis a Ã©crit : > we have more than a nice Git integration. I have been using Github for > my pharo project for over a year now without any issue, the last few > months I have been using gitfiltree which is making it even easier. > Definitely beats the alternatives . > Hi! Did you try to use git on a big project with a team? Did you try to merge .st files ? I heard it's really annoying to merge files with meta informations on git. An other point is that git file tree will not work on Windows if we do not fix the problem of the stdio. And a lot of people out of the community use Windows, so this is not a issue we should forget. Most of the people I know in company use Windows, so if we want to attract people this problem need to be corrected. > On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > â¦ Pharo may be within the 30 most popular languages on Earth. > The 30th languages has 3,253 repository. There are 2,635 on > SmalltalkHub. > > I wish we had a nice Git integration. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Cheers Cyril

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Dimitris Chloupis

This is the first time I read that one had to customise .gitattribute and other configurations to get git running with pharo. I have never needed to do any of those things, for me its just a matter of doing a single click, for installing gitfiletree. Then I add my git project like any other smalltalkhub project and manage it the same way via monticello. Maybe describe the exact issues you are having so others can help you out ? Frankly Pharo is far better than any other language I have used git with. What other language come with IDE included , and one that also integrates with Git out of the box without having to use the terminal ? I dont even remember doing anything the easy way in Java , Python maybe, Java ? nope. Bottom line is that each has a different experience, you say that Git integration is not nice, I say its the best experience I have every had with any other language. Obviously our experiences are like night and day . On the other hand I use the very basics of git, just git commit and git push/ pull. Maybe you have found some problems I have not. Please share, report so we can improve. On Sun, Sep 27, 2015 at 1:22 PM Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I have tried several times to use Git for my project. But I do not want to > spend time on configuring .gitattribute and other configuration file. This > does not go in the right direction I believe. Why is it easier to use git > with Java than it is with Pharo? > > Alexandre > > > > On Sep 27, 2015, at 12:11 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > we have more than a nice Git integration. I have been using Github for > my pharo project for over a year now without any issue, the last few months > I have been using gitfiltree which is making it even easier. Definitely > beats the alternatives . > > > > On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > â¦ Pharo may be within the 30 most popular languages on Earth. > > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > > > I wish we had a nice Git integration. > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by philippe.back＠highoctane.be

It isn't. It is actually very easy to use git. Time for a video :-) Expect that for tomorrow. Phil Le 27 sept. 2015 12:22, "Alexandre Bergel" <alexandre.bergel(a)me.com> a Ã©crit : > I have tried several times to use Git for my project. But I do not want to > spend time on configuring .gitattribute and other configuration file. This > does not go in the right direction I believe. Why is it easier to use git > with Java than it is with Pharo? > > Alexandre > > > > On Sep 27, 2015, at 12:11 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > we have more than a nice Git integration. I have been using Github for > my pharo project for over a year now without any issue, the last few months > I have been using gitfiltree which is making it even easier. Definitely > beats the alternatives . > > > > On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > > â¦ Pharo may be within the 30 most popular languages on Earth. > > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > > > I wish we had a nice Git integration. > > > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Alexandre Bergel

I have tried several times to use Git for my project. But I do not want to spend time on configuring .gitattribute and other configuration file. This does not go in the right direction I believe. Why is it easier to use git with Java than it is with Pharo? Alexandre > On Sep 27, 2015, at 12:11 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > we have more than a nice Git integration. I have been using Github for my pharo project for over a year now without any issue, the last few months I have been using gitfiltree which is making it even easier. Definitely beats the alternatives . > > On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > â¦ Pharo may be within the 30 most popular languages on Earth. > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > I wish we had a nice Git integration. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Dimitris Chloupis

we have more than a nice Git integration. I have been using Github for my pharo project for over a year now without any issue, the last few months I have been using gitfiltree which is making it even easier. Definitely beats the alternatives . On Sun, Sep 27, 2015 at 12:58 PM Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > â¦ Pharo may be within the 30 most popular languages on Earth. > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > I wish we had a nice Git integration. > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Sept. 27, 2015

Re: [Pharo-dev] If all Pharo projects were on GitHub...

by Volkert

+1 On 27.09.2015 11:57, Alexandre Bergel wrote: > â¦ Pharo may be within the 30 most popular languages on Earth. > The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. > > I wish we had a nice Git integration. > > Alexandre

Sept. 27, 2015

If all Pharo projects were on GitHub...

by Alexandre Bergel

â¦ Pharo may be within the 30 most popular languages on Earth. The 30th languages has 3,253 repository. There are 2,635 on SmalltalkHub. I wish we had a nice Git integration. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 27, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

Le 25/09/2015 19:35, stepharo a Ã©crit : > I would keep ## if in the future we need a new syntactic sugaring construct. Why keep it if it is easy to add once you know you need it? For now, this code allows things like: RBParser parseExpression: '#####################################t' Note on all those funny symbol syntaxes: formatting will get rid of them. Another fun syntax example: RBParser parseExpression: '#" I am a quite long comment" t' Thierry > Le 25/9/15 09:01, Nicolai Hess a Ã©crit : >> >> >> 2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com >> <mailto:thierry.goubier@gmail.com>>: >> >> Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : >> >> >> >> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k >> <<mailto:i.uhnak@gmail.com>i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>>>: >> >> > - 250 * 1.5 returns -2.25 >> >> why is this valid syntax? >> >> >> >> I don't know if this is valid syntax (I always wondered that >> there is >> one place in PointTest, that is not compilable with old >> compiler but >> compiles >> fine with opal). >> But the error happens in >> RBParser>>#parseNegatedNumber. >> If a #- is recognized, it tests if a literalnumber follows >> (but from the >> token stream, that is, the spaces are ignored). >> Now the real bug is, that we do two "steps" and concstruct a new >> literalvaluenode from the now following tokens. >> RBParser parseExpression:'- 2' -> throws an error, because no >> following >> tokens >> RBParser parseExpression:'- 2 * 3' -> works but actually >> duplicates the >> two last tokens "*3 *3. >> and some funny other things '- 2@1' -> '-1@1' >> >> >> Another one I found in the tests: would you expect >> >> RBParser parseExpression: '# >> >> 1 = 1' >> >> To be the same thing as '#1 = 1' ? >> >> >> >> And another one: >> #t = ##t "-> true" >> >> I thnk ##t should be allowed. >> >> >> Thierry >> >> >

Sept. 27, 2015

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by stepharo

Hi Eliot Thanks for the discussion. I will archive it and reread it. Now I think that historically they missed several points I learned while working on the Moose file format: - having doit or expressions to be executed instead of a declaration puts the burden on the tools. - for example not having a class definition declaration and just a do it forces the tools to parse and guess. - relying on sequence is not good because if you file is cut then this impacts several entities instead of having just one impacted. - I do not get why each entity in the chunk format is not self contained because in any case no decent programmer would use it to write code. - Mixing annotation and essential information makes the format really verbose. - what we see is that if we want to exchange on mail about code in several method in different classes, the chunk format is a pain vs. Point >> signature [ code here ] - This is not by accident that in all the books we wrote we use Clas >> signature code This way is not good because we do not have the warranty that code is not cut. Hence the previous one is better. I will restart one of these days to work on an alternate file format for textual editor. I do not like the GNUSt syntax. Now indeed how to store metadata is a good question. Stef

Sept. 27, 2015

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

by stepharo

Le 9/9/15 11:21, Nicolas Cellier a Ã©crit : > Note that when:send:to: already existed in VW before announcements (it > did work with a symbol like when: #someAspectChanged send: #someAction > to: self, and this was tiggered thru dependents mechanism - self > changed: #someAspectChanged...). yes > IMO, it is very expressive, whatever the underlying mechanism > (dependents or Announcement). + 1 > > 2015-09-09 8:49 GMT+02:00 Norbert Hartl <norbert(a)hartl.name > <mailto:norbert@hartl.name>>: > > > > > > > Am 08.09.2015 um 22:49 schrieb stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > > Me too :) > > I do not care that they is a registration mechanism behind. > > > But you get a subscription back. Und the user should be aware of > that there is no magical unsubscribe mechanism. So this no reason > for me but I still like when:send:to: better although it feels a > bit awkward. > > Norbert > > Stef > > > > Le 8/9/15 16:30, Ferlicot D. Cyril a Ã©crit : > >> Le 08/09/2015 10:13, Stephan Eggermont a Ã©crit : > >> > >>> When looking at the implementation, it looks as if we should > >>> replace all #when:send:to: by #subscribe:when:do:, not the > other way > >>> around. > >>> > >>> Where is this all coming from? > >>> > >>> Stephan > >> I think that #when:send:to: is more explicit and more > understandable, > >> but this is a personal opinion. > > > > > >

Sept. 27, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

Le 25/09/2015 13:01, Marcus Denker a Ã©crit : > >> On 25 Sep 2015, at 09:53, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Note for ref on the original point: >> >> ANSI Smalltalk allow for space between - and the number token. Squeak is then non A >> >> For the new point: >> >> ANSI Smalltalk does not allow for space between # and the selector, or between # and the quoted string. >> >> Should be an easy fix. >> >> Marcus, how do we should validate RBParser changes? Reparse all the code in the image and compares ASTs? >> > Yes, I think soâ¦ it would of course be better to have a larger scale regression test suite, but for now ârecompiling the imageâ > is the thing we do to check the compiler Reparsing the whole image shows 7 uses of # <space> something and #number. Thierry > Marcus > > >

Sept. 26, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by stepharo

During the lecture I saw that {(10@20) . (30@40)} is printed as {(10@20). (30@40)} and I think that it would much nicer to have {(10@20) . (30@40)}

Sept. 26, 2015

Some news from the growing pharo teacher front

by stepharo

Hi guys I want to let you know that there will be a new pharo lecture in YaoundÃ©. I presented Pharo during a seminar and the previous minister of education was there and asked us to do a lecture. In June we did it with Damien C. by skype. And now there is an official lecture at YaoundÃ© given by Prof. Metalagia. This is an excellent news. I will give some lectures in december there. In Togo my first visit was quite successful: 120 participants to the conferences I gave (it was still vacation time there). There were 60 students following lectures from 8h to 17h during 4 days... Yes I'm exhausted ;) A new Pharo lecture will start in north Togo. I will go back in December. One of the idea is to help students to get good in Pharo and pharo web stack and build web apps and other. I hope that we can have within 2/3 year There is a competition AppTogo. People are learning C# and others. I hope that some students will compete with Pharo so I will be looking for potential mentors to help them. Giving them advices, pointing them to the right solution/framework and may be a bit of pair rogramming if skype works. I distributed the Pharo Starter Kit (we will announce it officially now that I have 10 gb space on my server) People love the Youtube videos folder I'm collecting. Yes internet is a pain there. Chloupis I put your great youtube tutorial! Thanks for it. some students watched it. Stef

Sept. 26, 2015

Some news from the growing pharo teacher front

by stepharo

Hi guys I want to let you that there will be a new pharo lecture in YaoundÃ©. I presented Pharo during a seminar and the previous minister of education was there and asked us to do a lecture in June. We did it with Damien C. by skype. And now there is an official lecture at YaoundÃ© given by Prof. Metalagia. This is an excellent news. In Togo my first visit was quite successful: 120 participants to the conferences I gave (it was still vacation time there). There were 60 students following lectures from 8h to 17h during 4 days... Yes I'm exhausted. A new Pharo lecture will start in north Togo. I will go back in December. One of the idea is to help students to get good in Pharo and build web app and other. There is a competition AppTogo. People are learning C# and others. I hope that some students will com

Sept. 26, 2015

Re: [Pharo-dev] [Reflectivity] What are the #arguments?

by Marcus Denker

> On 25 Sep 2015, at 13:02, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Good idea, I will add #availableReifications > https://pharo.fogbugz.com/f/cases/16642/availableReifications-return-the-li… <https://pharo.fogbugz.com/f/cases/16642/availableReifications-return-the-li…> I decided to return the symbolic encoded that is used when setting up the links: testAvailableReifications self assert: (RBMessageNode new availableReifications includes: #receiver). self deny: (RBMessageNode new availableReifications includes: #value). self assert: ((ReflectivityExamples classVariableNamed: #ClassVar) availableReifications includes: #name). self deny: ((ReflectivityExamples classVariableNamed: #ClassVar) availableReifications includes: #selector). (ReflectivityExamples classVariableNamed: #ClassVar) availableReifications ==> "#(#value #name)â Marcus

Sept. 26, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Ben Coman

On Sat, Sep 26, 2015 at 4:17 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2015-09-25 21:16 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >> Hi Nicolas, >> >> On Thu, Sep 24, 2015 at 5:01 AM, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> >>> >>> >>> 2015-09-24 13:23 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >>>> >>>> Then, given that negative numbers are correctly tokenified by the >>>> RBParser, I would remove that logic in Pharo's RBParser. >>>> >>>> (From a front-end implementor point of view, I also would have no issue >>>> with someone specifying a negative literal as - (\s)* [0-9]+ either. There >>>> is so much silliness in your average language front-end anyway). >>>> >>> >>> My grief was the interpretation of literal arrays: #(1 - 2) is currently >>> not #(1 -2), so if space is gobbled at tokenization, that's a semantic >>> shift... >>> Do we want to keep #(1 - 2) or shall we force some more pedantic #(1 #- >>> 2)? >> >> >> We should keep #(1 - 2) provided it is interpreted as #(1 #'-' 2). The # >> tags are noisy (if not ugly) and have never been necessary for literal >> symbols inside arrays. -2 is quite different from - 2. >> > > Agree, that's one good reason to not accept - 2 as a valid literal, for me > it's different than -2. > Separators have one semantic: they separrate. > white spaces are separators. Indeed. With '-2' being the literal, its a consideration of whether whitespace is allowed within a literal. Otherwise '1 - - 1' should evaluate to 2 ?? Currently it errors, which seems correct. '1 - -1' evaluates correctly to 2. > > >> >> Also why do you think this means? >> >> 1.0 >> >> Given that this means two different statements >> >> nil.nil >> >> IMO, . as a statement separator should be followed by whitespace to >> eliminate this ambiguity. i.e. nil.nil would be a syntax error, and nil. >> nil would be acceptable. This opens up the use of . in selectors to do cool >> things like the old multiple inheritance syntax where one could do directed >> sends such as super Dictionary.at: key if in a subclass with multiple >> superclasses and wanting to disambiguate which of multiple superclass >> implementations one wanted to invoke. > > > Dan said that he didn't want to make the separator mandatory, but I guess he > meant to apply this rule to an expression. > Forcing a separator between sentences would not hurt IMO too. > In any case, I never saw code written without separators between sentences. This sounds reasonable to me. cheers -ben > >> >> >> >>> >>> >>>> >>>> What is the state of RBParser in Squeak about that? >>> >>> >>> RBParser is not in trunk, it's an add-on. >>> No idea which/where is the latest Squeak-compatible version... >>> >>>> >>>> >>>> Thierry >>>> >>>> >>>> 2015-09-24 12:03 GMT+02:00 Nicolas Cellier >>>> <nicolas.cellier.aka.nice(a)gmail.com>: >>>>> >>>>> Oh, and I suspect an instability in the numbering of squeak-dev >>>>> archive... >>>>> The reference thread is (today) >>>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2006-May/103684.html >>>>> >>>>> 2015-09-24 11:39 GMT+02:00 Nicolas Cellier >>>>> <nicolas.cellier.aka.nice(a)gmail.com>: >>>>>> >>>>>> A space used to be accepted between minus sign and number in old >>>>>> versions of Squeak compiler (before 2010) >>>>>> But I doubt this was decided on purpose. >>>>>> IMO it was more a side effect of the implementation, which had messy >>>>>> corners >>>>>> (the fact that the tokenizer did produce two tokens $- and positive >>>>>> number) >>>>>> >>>>>> I would add that this was undocumented, dialect specific, and a false >>>>>> good idea letting newbies think that they can use unary prefixed >>>>>> operators... >>>>>> There is no such thing in the language. >>>>>> >>>>>> Oh, and this even has changed in Squeak a few years ago: >>>>>> >>>>>> ------------------------------------------------------- >>>>>> >>>>>> http://source.squeak.org/trunk/Compiler-nice.120.mcz >>>>>> >>>>>> ==================== Summary ==================== >>>>>> >>>>>> Name: Compiler-nice.120 >>>>>> Author: nice >>>>>> Time: 23 February 2010, 5:14:44.049 pm >>>>>> UUID: 9429cc05-281b-484e-94c2-bd0baf4f5230 >>>>>> Ancestors: Compiler-nice.119 >>>>>> >>>>>> Authorize - at any position in binary selectors (like VW 7.7) >>>>>> See http://bugs.squeak.org/view.php?id=3616 >>>>>> Address the problem of compiling 1@-2 with following strategy: >>>>>> >>>>>> If compiler is non interactive, then compile with backward >>>>>> compatibility 1 @ (-2). >>>>>> If compiler is interactive, propose a menu to disambiguate and insert >>>>>> a proper space. >>>>>> 1@ -2 -> MessageSend receiver: 1 selector: #'@' argument: -2 >>>>>> 1@- 2 -> MessageSend receiver: 1 selector: #'@-' argument: 2 >>>>>> >>>>>> Warning: Squeak did understand (1@- 2) as (1 @ (-2)).... >>>>>> I didn't do anything to support this vicious Squeakism, and by now the >>>>>> semantics are change. >>>>>> >>>>>> >>>>>> 2015-09-24 9:25 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>>>>>>> >>>>>>>> > - 250 * 1.5 returns -2.25 >>>>>>>> >>>>>>>> why is this valid syntax? >>>>>>> >>>>>>> >>>>>>> It should not. RBParser bug. This is not valid Smalltalk syntax. As >>>>>>> Ben showed similar cases raise an error but this one generate incorrect >>>>>>> compiledMethod instead. >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Sep 24, 2015 at 5:35 AM, Ben Coman <btc(a)openinworld.com> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> RBParser parseExpression: '-250 * 1.5' => "RBMessageNode(-250 * >>>>>>>>> 1.5)" >>>>>>>>> RBParser parseExpression: '- 250 * 1.5' => "RBMessageNode(*1.5 >>>>>>>>> * 1.5)" >>>>>>>>> >>>>>>>>> RBParser parseExpression: '250 * -1.5' => "RBMessageNode(250 * >>>>>>>>> -1.5)" >>>>>>>>> RBParser parseExpression: '250 * - 1.5' => MNU >>>>>>>>> RBToken>>realvalue. >>>>>>>>> >>>>>>>>> RBParser parseExpression: '-250' => "RBLiteralValueNode(-250)" >>>>>>>>> RBParser parseExpression: '- 250' => MNU RBToken>>realvalue. >>>>>>>>> >>>>>>>>> So how significant should be the space between the negative sign >>>>>>>>> and its number? >>>>>>>>> >>>>>>>>> cheers -ben >>>>>>>>> >>>>>>>>> On Thu, Sep 24, 2015 at 6:34 AM, ClÃ©ment Bera >>>>>>>>> <bera.clement(a)gmail.com> wrote: >>>>>>>>> > RBParser parseExpression: '- 250 * 1.5' => Answers >>>>>>>>> > RBMessageNode(*1.5 * >>>>>>>>> > 1.5) >>>>>>>>> > >>>>>>>>> > Second expression looks correct. >>>>>>>>> > >>>>>>>>> > Hence RBParser bug. >>>>>>>>> > >>>>>>>>> > 2015-09-23 23:42 GMT+02:00 phil(a)highoctane.be >>>>>>>>> > <phil(a)highoctane.be>: >>>>>>>>> >> >>>>>>>>> >> debug it on the first one gives "MNU: receiver of >>>>>>>>> >> "doSemanticAnalyisIn:" >>>>>>>>> >> is nil. >>>>>>>>> >> >>>>>>>>> >> Weird. >>>>>>>>> >> >>>>>>>>> >> On Wed, Sep 23, 2015 at 8:40 AM, stepharo <stepharo(a)free.fr> >>>>>>>>> >> wrote: >>>>>>>>> >>> >>>>>>>>> >>> Hi guys >>>>>>>>> >>> >>>>>>>>> >>> I think that this is quite bad that >>>>>>>>> >>> - 250 * 1.5 returns -2.25 >>>>>>>>> >>> >>>>>>>>> >>> while >>>>>>>>> >>> >>>>>>>>> >>> -250 * 1.5 return 375 >>>>>>>>> >>> >>>>>>>>> >>> stef >>>>>>>>> >>> >>>>>>>>> >> >>>>>>>>> > >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot > >

Sept. 26, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Nicolas Cellier

2015-09-25 21:16 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Nicolas, > > On Thu, Sep 24, 2015 at 5:01 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> >> >> 2015-09-24 13:23 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> Then, given that negative numbers are correctly tokenified by the >>> RBParser, I would remove that logic in Pharo's RBParser. >>> >>> (From a front-end implementor point of view, I also would have no issue >>> with someone specifying a negative literal as - (\s)* [0-9]+ either. There >>> is so much silliness in your average language front-end anyway). >>> >>> >> My grief was the interpretation of literal arrays: #(1 - 2) is currently >> not #(1 -2), so if space is gobbled at tokenization, that's a semantic >> shift... >> Do we want to keep #(1 - 2) or shall we force some more pedantic #(1 #- >> 2)? >> > > We should keep #(1 - 2) provided it is interpreted as #(1 #'-' 2). The # > tags are noisy (if not ugly) and have never been necessary for literal > symbols inside arrays. -2 is quite different from - 2. > > Agree, that's one good reason to not accept - 2 as a valid literal, for me it's different than -2. Separators have one semantic: they separrate. white spaces are separators. > Also why do you think this means? > > 1.0 > > Given that this means two different statements > > nil.nil > > IMO, . as a statement separator should be followed by whitespace to > eliminate this ambiguity. i.e. nil.nil would be a syntax error, and nil. > nil would be acceptable. This opens up the use of . in selectors to do > cool things like the old multiple inheritance syntax where one could do > directed sends such as super Dictionary.at: key if in a subclass with > multiple superclasses and wanting to disambiguate which of multiple > superclass implementations one wanted to invoke. > Dan said that he didn't want to make the separator mandatory, but I guess he meant to apply this rule to an expression. Forcing a separator between sentences would not hurt IMO too. In any case, I never saw code written without separators between sentences. > > >> >> >>> What is the state of RBParser in Squeak about that? >>> >> >> RBParser is not in trunk, it's an add-on. >> No idea which/where is the latest Squeak-compatible version... >> >> >>> >>> Thierry >>> >>> >>> 2015-09-24 12:03 GMT+02:00 Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com>: >>> >>>> Oh, and I suspect an instability in the numbering of squeak-dev >>>> archive... >>>> The reference thread is (today) >>>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2006-May/103684.html >>>> >>>> 2015-09-24 11:39 GMT+02:00 Nicolas Cellier < >>>> nicolas.cellier.aka.nice(a)gmail.com>: >>>> >>>>> A space used to be accepted between minus sign and number in old >>>>> versions of Squeak compiler (before 2010) >>>>> But I doubt this was decided on purpose. >>>>> IMO it was more a side effect of the implementation, which had messy >>>>> corners >>>>> (the fact that the tokenizer did produce two tokens $- and positive >>>>> number) >>>>> >>>>> I would add that this was undocumented, dialect specific, and a false >>>>> good idea letting newbies think that they can use unary prefixed >>>>> operators... >>>>> There is no such thing in the language. >>>>> >>>>> Oh, and this even has changed in Squeak a few years ago: >>>>> >>>>> ------------------------------------------------------- >>>>> >>>>> http://source.squeak.org/trunk/Compiler-nice.120.mcz >>>>> >>>>> ==================== Summary ==================== >>>>> >>>>> Name: Compiler-nice.120 >>>>> Author: nice >>>>> Time: 23 February 2010, 5:14:44.049 pm >>>>> UUID: 9429cc05-281b-484e-94c2-bd0baf4f5230 >>>>> Ancestors: Compiler-nice.119 >>>>> >>>>> Authorize - at any position in binary selectors (like VW 7.7) >>>>> See http://bugs.squeak.org/view.php?id=3616 >>>>> Address the problem of compiling 1@-2 with following strategy: >>>>> >>>>> If compiler is non interactive, then compile with backward >>>>> compatibility 1 @ (-2). >>>>> If compiler is interactive, propose a menu to disambiguate and insert >>>>> a proper space. >>>>> 1@ -2 -> MessageSend receiver: 1 selector: #'@' argument: -2 >>>>> 1@- 2 -> MessageSend receiver: 1 selector: #'@-' argument: 2 >>>>> >>>>> Warning: Squeak did understand (1@- 2) as (1 @ (-2)).... >>>>> I didn't do anything to support this vicious Squeakism, and by now the >>>>> semantics are change. >>>>> >>>>> >>>>> 2015-09-24 9:25 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>>> >>>>>> >>>>>> >>>>>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>>>>> >>>>>>> > - 250 * 1.5 returns -2.25 >>>>>>> >>>>>>> why is this valid syntax? >>>>>>> >>>>>> >>>>>> It should not. RBParser bug. This is not valid Smalltalk syntax. As >>>>>> Ben showed similar cases raise an error but this one generate incorrect >>>>>> compiledMethod instead. >>>>>> >>>>>> >>>>>>> >>>>>>> On Thu, Sep 24, 2015 at 5:35 AM, Ben Coman <btc(a)openinworld.com> >>>>>>> wrote: >>>>>>> >>>>>>>> RBParser parseExpression: '-250 * 1.5' => "RBMessageNode(-250 * >>>>>>>> 1.5)" >>>>>>>> RBParser parseExpression: '- 250 * 1.5' => "RBMessageNode(*1.5 >>>>>>>> * 1.5)" >>>>>>>> >>>>>>>> RBParser parseExpression: '250 * -1.5' => "RBMessageNode(250 * >>>>>>>> -1.5)" >>>>>>>> RBParser parseExpression: '250 * - 1.5' => MNU >>>>>>>> RBToken>>realvalue. >>>>>>>> >>>>>>>> RBParser parseExpression: '-250' => "RBLiteralValueNode(-250)" >>>>>>>> RBParser parseExpression: '- 250' => MNU RBToken>>realvalue. >>>>>>>> >>>>>>>> So how significant should be the space between the negative sign >>>>>>>> and its number? >>>>>>>> >>>>>>>> cheers -ben >>>>>>>> >>>>>>>> On Thu, Sep 24, 2015 at 6:34 AM, ClÃ©ment Bera < >>>>>>>> bera.clement(a)gmail.com> wrote: >>>>>>>> > RBParser parseExpression: '- 250 * 1.5' => Answers >>>>>>>> RBMessageNode(*1.5 * >>>>>>>> > 1.5) >>>>>>>> > >>>>>>>> > Second expression looks correct. >>>>>>>> > >>>>>>>> > Hence RBParser bug. >>>>>>>> > >>>>>>>> > 2015-09-23 23:42 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be >>>>>>>> >: >>>>>>>> >> >>>>>>>> >> debug it on the first one gives "MNU: receiver of >>>>>>>> "doSemanticAnalyisIn:" >>>>>>>> >> is nil. >>>>>>>> >> >>>>>>>> >> Weird. >>>>>>>> >> >>>>>>>> >> On Wed, Sep 23, 2015 at 8:40 AM, stepharo <stepharo(a)free.fr> >>>>>>>> wrote: >>>>>>>> >>> >>>>>>>> >>> Hi guys >>>>>>>> >>> >>>>>>>> >>> I think that this is quite bad that >>>>>>>> >>> - 250 * 1.5 returns -2.25 >>>>>>>> >>> >>>>>>>> >>> while >>>>>>>> >>> >>>>>>>> >>> -250 * 1.5 return 375 >>>>>>>> >>> >>>>>>>> >>> stef >>>>>>>> >>> >>>>>>>> >> >>>>>>>> > >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > > > -- > _,,,^..^,,,_ > best, Eliot >

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Eliot Miranda

Hi Nicolas, On Thu, Sep 24, 2015 at 5:01 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2015-09-24 13:23 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Then, given that negative numbers are correctly tokenified by the >> RBParser, I would remove that logic in Pharo's RBParser. >> >> (From a front-end implementor point of view, I also would have no issue >> with someone specifying a negative literal as - (\s)* [0-9]+ either. There >> is so much silliness in your average language front-end anyway). >> >> > My grief was the interpretation of literal arrays: #(1 - 2) is currently > not #(1 -2), so if space is gobbled at tokenization, that's a semantic > shift... > Do we want to keep #(1 - 2) or shall we force some more pedantic #(1 #- 2)? > We should keep #(1 - 2) provided it is interpreted as #(1 #'-' 2). The # tags are noisy (if not ugly) and have never been necessary for literal symbols inside arrays. -2 is quite different from - 2. Also why do you think this means? 1.0 Given that this means two different statements nil.nil IMO, . as a statement separator should be followed by whitespace to eliminate this ambiguity. i.e. nil.nil would be a syntax error, and nil. nil would be acceptable. This opens up the use of . in selectors to do cool things like the old multiple inheritance syntax where one could do directed sends such as super Dictionary.at: key if in a subclass with multiple superclasses and wanting to disambiguate which of multiple superclass implementations one wanted to invoke. > > >> What is the state of RBParser in Squeak about that? >> > > RBParser is not in trunk, it's an add-on. > No idea which/where is the latest Squeak-compatible version... > > >> >> Thierry >> >> >> 2015-09-24 12:03 GMT+02:00 Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com>: >> >>> Oh, and I suspect an instability in the numbering of squeak-dev >>> archive... >>> The reference thread is (today) >>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2006-May/103684.html >>> >>> 2015-09-24 11:39 GMT+02:00 Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com>: >>> >>>> A space used to be accepted between minus sign and number in old >>>> versions of Squeak compiler (before 2010) >>>> But I doubt this was decided on purpose. >>>> IMO it was more a side effect of the implementation, which had messy >>>> corners >>>> (the fact that the tokenizer did produce two tokens $- and positive >>>> number) >>>> >>>> I would add that this was undocumented, dialect specific, and a false >>>> good idea letting newbies think that they can use unary prefixed >>>> operators... >>>> There is no such thing in the language. >>>> >>>> Oh, and this even has changed in Squeak a few years ago: >>>> >>>> ------------------------------------------------------- >>>> >>>> http://source.squeak.org/trunk/Compiler-nice.120.mcz >>>> >>>> ==================== Summary ==================== >>>> >>>> Name: Compiler-nice.120 >>>> Author: nice >>>> Time: 23 February 2010, 5:14:44.049 pm >>>> UUID: 9429cc05-281b-484e-94c2-bd0baf4f5230 >>>> Ancestors: Compiler-nice.119 >>>> >>>> Authorize - at any position in binary selectors (like VW 7.7) >>>> See http://bugs.squeak.org/view.php?id=3616 >>>> Address the problem of compiling 1@-2 with following strategy: >>>> >>>> If compiler is non interactive, then compile with backward >>>> compatibility 1 @ (-2). >>>> If compiler is interactive, propose a menu to disambiguate and insert >>>> a proper space. >>>> 1@ -2 -> MessageSend receiver: 1 selector: #'@' argument: -2 >>>> 1@- 2 -> MessageSend receiver: 1 selector: #'@-' argument: 2 >>>> >>>> Warning: Squeak did understand (1@- 2) as (1 @ (-2)).... >>>> I didn't do anything to support this vicious Squeakism, and by now the >>>> semantics are change. >>>> >>>> >>>> 2015-09-24 9:25 GMT+02:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: >>>> >>>>> >>>>> >>>>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >>>>> >>>>>> > - 250 * 1.5 returns -2.25 >>>>>> >>>>>> why is this valid syntax? >>>>>> >>>>> >>>>> It should not. RBParser bug. This is not valid Smalltalk syntax. As >>>>> Ben showed similar cases raise an error but this one generate incorrect >>>>> compiledMethod instead. >>>>> >>>>> >>>>>> >>>>>> On Thu, Sep 24, 2015 at 5:35 AM, Ben Coman <btc(a)openinworld.com> >>>>>> wrote: >>>>>> >>>>>>> RBParser parseExpression: '-250 * 1.5' => "RBMessageNode(-250 * 1.5)" >>>>>>> RBParser parseExpression: '- 250 * 1.5' => "RBMessageNode(*1.5 * >>>>>>> 1.5)" >>>>>>> >>>>>>> RBParser parseExpression: '250 * -1.5' => "RBMessageNode(250 * >>>>>>> -1.5)" >>>>>>> RBParser parseExpression: '250 * - 1.5' => MNU >>>>>>> RBToken>>realvalue. >>>>>>> >>>>>>> RBParser parseExpression: '-250' => "RBLiteralValueNode(-250)" >>>>>>> RBParser parseExpression: '- 250' => MNU RBToken>>realvalue. >>>>>>> >>>>>>> So how significant should be the space between the negative sign and >>>>>>> its number? >>>>>>> >>>>>>> cheers -ben >>>>>>> >>>>>>> On Thu, Sep 24, 2015 at 6:34 AM, ClÃ©ment Bera < >>>>>>> bera.clement(a)gmail.com> wrote: >>>>>>> > RBParser parseExpression: '- 250 * 1.5' => Answers >>>>>>> RBMessageNode(*1.5 * >>>>>>> > 1.5) >>>>>>> > >>>>>>> > Second expression looks correct. >>>>>>> > >>>>>>> > Hence RBParser bug. >>>>>>> > >>>>>>> > 2015-09-23 23:42 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be >>>>>>> >: >>>>>>> >> >>>>>>> >> debug it on the first one gives "MNU: receiver of >>>>>>> "doSemanticAnalyisIn:" >>>>>>> >> is nil. >>>>>>> >> >>>>>>> >> Weird. >>>>>>> >> >>>>>>> >> On Wed, Sep 23, 2015 at 8:40 AM, stepharo <stepharo(a)free.fr> >>>>>>> wrote: >>>>>>> >>> >>>>>>> >>> Hi guys >>>>>>> >>> >>>>>>> >>> I think that this is quite bad that >>>>>>> >>> - 250 * 1.5 returns -2.25 >>>>>>> >>> >>>>>>> >>> while >>>>>>> >>> >>>>>>> >>> -250 * 1.5 return 375 >>>>>>> >>> >>>>>>> >>> stef >>>>>>> >>> >>>>>>> >> >>>>>>> > >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -- _,,,^..^,,,_ best, Eliot

Sept. 25, 2015

Re: [Pharo-dev] System-Announcements: add a ProtocolRenamed announcement

by stepharo

Thanks thierry to look and discuss these points. I do not have enough calm time to get any concentration (of course I was teaching all day long). Stef Le 16/9/15 09:20, Thierry Goubier a Ã©crit : > > > 2015-09-16 11:05 GMT+02:00 Skip Lentz <skip.lentz(a)inria.fr > <mailto:skip.lentz@inria.fr>>: > ... > >> >> One more thing. I hope that when renaming the protocol, the >> relevant MethodRecategorized are sent, because many things depend >> on that one. > > Yes, those are already sent. ProtocolRenamed, if implemented, > should be announced in addition to those. > >> I need to check AltBrowser behavior on this one. Renaming a >> protocol is not what I expected. It looks harmless, but it has >> important consequences if the protocol is an extension or an >> override. > > Alright, let me know. > > > I think you can go forward. If the MethodRecategorized is sent, then > it should be OK. > > >> >> Thanks for your reply :) >> >> PS: Thereâs something else related to System-Announcements, >> namely that when I rename a category I get no CategoryRenamed >> announcement. >> I will send an e-mail about that later. >> >> >> Hum, SystemOrganizer>>#renameCategory:toBe: sends it (in Pharo4). > > Indeed it does, but RPackageTag>>#renameTo:category: suspends the > SystemAnnouncer while it sends SystemOrganizer>>#renameCategory:toBe:. > I donât know why, Iâm interested to know. Because > RPackageTag>>#renameTo:category: is used when you rename a > category (in Nautilus, at least). > > > I would heed Esteban advice on that. If the system announcer is > suspended, then this is probably because we may have some kind of > infinite loop and / or a incoherent state while renaming the system > category. > > I'll have a look too. > > Thierry > > > Skip > >

Sept. 25, 2015

Re: [Pharo-dev] Reflectivity: Links that de-install themselves (oneShot)

by stepharo

Tx this is I think a good idea (adding the setter) Le 20/9/15 14:17, Marcus Denker a Ã©crit : >> On 19 Sep 2015, at 01:10, stepharo <stepharo(a)free.fr> wrote: >> >> Marcus I have a API design question >> >> when you offer >> >> options: #(optionOneShot); >> >> versus >> >> optionOneShot >> >> Do you do a perform of the arrays selectors? >> What is the benefit of options: > I needed a mechanism for flags (stored not each in an ivar, as they normally > not active). As we have this mechanism in Opal already, I decided to use the > same pattern. > As in Opal, for all the pre-defined options we should not rely on perform: but > have explicit #optionOneShot getter/setter methods. I will add those later.. > > Marcus > > >

Sept. 25, 2015

Some news from the growing pharo teacher front

by stepharo

Hi guys I want to let you know that there will be a new pharo lecture in YaoundÃ©. I presented Pharo during a seminar and the previous minister of education was there and asked us to do a lecture. In June we did it with Damien C. by skype. And now there is an official lecture at YaoundÃ© given by Prof. Metalagia. This is an excellent news. I will give some lectures in december there. In Togo my first visit was quite successful: 120 participants to the conferences I gave (it was still vacation time there). There were 60 students following lectures from 8h to 17h during 4 days... Yes I'm exhausted ;) A new Pharo lecture will start in north Togo. I will go back in December. One of the idea is to help students to get good in Pharo and pharo web stack and build web apps and other. I hope that we can have within 2/3 year startups there. The gouverment in really pushing in that direction. There is a competition AppTogo. People are learning C# and other languages. So nothing is that easy :). I hope that some students will compete with Pharo so I will be looking for potential mentors to help them. Because I will be busy working on the mooc and other actions. Giving them advices, pointing them to the right solution/framework and may be a bit of pair programming if skype works. I distributed the Pharo Starter Kit (we will announce it officially now that I have 10 gb space on my server) People loved the Youtube videos folder I'm collecting. Yes internet is a pain there and avoiding to crawl on a slow internet is a plus. In addition the videos shows that our community is doing crazy stuff. Chloupis I put your great youtube tutorial! Thanks for it. some students watched it. Stef

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by stepharo

I would keep ## if in the future we need a new syntactic sugaring construct. Le 25/9/15 09:01, Nicolai Hess a Ã©crit : > > > 2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>>: > > Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : > > > > 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com> > <mailto:i.uhnak@gmail.com <mailto:i.uhnak@gmail.com>>>: > > > - 250 * 1.5 returns -2.25 > > why is this valid syntax? > > > > I don't know if this is valid syntax (I always wondered that > there is > one place in PointTest, that is not compilable with old > compiler but > compiles > fine with opal). > But the error happens in > RBParser>>#parseNegatedNumber. > If a #- is recognized, it tests if a literalnumber follows > (but from the > token stream, that is, the spaces are ignored). > Now the real bug is, that we do two "steps" and concstruct a new > literalvaluenode from the now following tokens. > RBParser parseExpression:'- 2' -> throws an error, because no > following > tokens > RBParser parseExpression:'- 2 * 3' -> works but actually > duplicates the > two last tokens "*3 *3. > and some funny other things '- 2@1' -> '-1@1' > > > Another one I found in the tests: would you expect > > RBParser parseExpression: '# > > 1 = 1' > > To be the same thing as '#1 = 1' ? > > > > And another one: > #t = ##t "-> true" > > I thnk ##t should be allowed. > > > Thierry > >

Sept. 25, 2015

Re: [Pharo-dev] World.st has a new admin

by stepharo

thanks Sean this is great! Le 24/9/15 19:35, phil(a)highoctane.be a Ã©crit : > Sean, King of the World.st > > Thx for this!!!!! > > Phil > > On Thu, Sep 24, 2015 at 8:55 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > > I have always found the world.st <http://world.st> very very > useful. Thank you very much Geert. > And thanks Sean, you will do a great job as always. > > On Thu, Sep 24, 2015 at 3:09 PM, Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > > > On 24 Sep 2015, at 19:47, Stephan Eggermont > <stephan(a)stack.nl <mailto:stephan@stack.nl>> wrote: > > > > On 24/09/15 16:27, Geert Claes wrote: > >> The admin duties have now been handed over to Sean DeNigris > who kindly > >> volunteered to look after the www.world.st > <http://www.world.st> web presence as well as the > >> Nabble archived mailing list forums on forum.world.st > <http://forum.world.st>. > > > > Thank you Geert, for taking care of this important community > resource for us for so long, and Sean for stepping in and > taking over. > > +10 > > > Stephan > > > > > > -- > Mariano > http://marianopeck.wordpress.com > >

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

2015-09-25 13:01 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: > > > On 25 Sep 2015, at 09:53, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > Note for ref on the original point: > > > > ANSI Smalltalk allow for space between - and the number token. Squeak is > then non A > > > > For the new point: > > > > ANSI Smalltalk does not allow for space between # and the selector, or > between # and the quoted string. > > > > Should be an easy fix. > > > > Marcus, how do we should validate RBParser changes? Reparse all the code > in the image and compares ASTs? > > > Yes, I think soâ¦ it would of course be better to have a larger scale > regression test suite, but for now ârecompiling the imageâ > is the thing we do to check the compiler > Ok. My issue was a kind of versionning effect on the parser, and a process like: - recover and store all asts for all methods - apply a change to RBParser - reparse all methods one by one and compare ASTs with previous We have good GUI tools for manipulating packages, but sometimes I'd like to have a branch concept inside the image which says: - revert to master, - do something, - switch to branch (and load your changes), - continue something to validate Thierry > > Marcus > > >

Sept. 25, 2015

Re: [Pharo-dev] [Reflectivity] What are the #arguments?

by Marcus Denker

Good idea, I will add #availableReifications Marcus > On 25 Sep 2015, at 10:02, roberto.minelli(a)usi.ch wrote: > > Thank you very much, Marcus! > > Concerning the table..we can do a method that lists the #availableReifications or something like that ;) > > For example, if I am interested in all the available reifications for an RBMethodNode I can do: > RFReification subclasses select: [ :e | e nodes includesAny: RBMethodNode withAllSuperclasses ]. > > Cheers, > Roby > > >> On 25 Sep 2015, at 09:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hello, >> >> every one of these âreificationsâ are defined as a subclass of >> RFReification >> >> There is one subclass for every symbol (e.g. for #arguments, there is RFArgumentsReification). >> The class side method #key defines the exact symbol, while #nodes returns the AST node classes >> where this reification is available. >> >> I will make a full table soon that lists everything. >> >> Marcus >> >>> On 25 Sep 2015, at 09:36, roberto.minelli(a)usi.ch wrote: >>> >>> Dear Marcus, >>> >>> I am wondering where to âdiscoverâ all the possible values for the #arguments: to pass to the MetaLink. >>> >>> Cheers, >>> R >>> >> >

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Marcus Denker

> On 25 Sep 2015, at 09:53, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Note for ref on the original point: > > ANSI Smalltalk allow for space between - and the number token. Squeak is then non A > > For the new point: > > ANSI Smalltalk does not allow for space between # and the selector, or between # and the quoted string. > > Should be an easy fix. > > Marcus, how do we should validate RBParser changes? Reparse all the code in the image and compares ASTs? > Yes, I think soâ¦ it would of course be better to have a larger scale regression test suite, but for now ârecompiling the imageâ is the thing we do to check the compiler Marcus

Sept. 25, 2015

Re: [Pharo-dev] SHRBTextStyler and workspace/playground variables

by Marcus Denker

> On 25 Sep 2015, at 11:10, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > > On Fri, Sep 25, 2015 at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: > > > 2015-09-24 12:06 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>>: > Hi, > > Currently SHRBTextStyler does not highlight variables in the playground. > This could be added by extending SHRBTextStyler >>#resolveStyleFor: with > > workspace > ifNotNil: [(workspace hasBindingOf: aVariableNode name) > ifTrue: [^ #workspaceVar]]. > > Yes, I tried it already, but I couldn't get it to work. > I would like to have some way to add this to the semantic analyser step. > If the workspace is defined as a requestore scope, the variable analysis > should work the same way as if we actual "compile" the code. > > I also think this would be a much nicer solution. I looked a bit at the how requestor scopes > work but it's not that clear how to add the workspace as a scope. > > That actually is what needs to be doneâ¦ it is on my TODOâ¦ Marcus

Sept. 25, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50342 Home: https://github.com/pharo-project/pharo-core

Sept. 25, 2015

[pharo-project/pharo-core] d938ca: 50342

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d938ca3b9035a8b02420be64a38bf1685c94ef51 https://github.com/pharo-project/pharo-core/commit/d938ca3b9035a8b02420be64… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-25 (Fri, 25 Sep 2015) Changed paths: M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeClassVariable.st M Reflectivity-Tests.package/ReflectivityExamples.class/instance/initialization/initialize.st M Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/running/tearDown.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyGlobalName.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyGlobalValue.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyGlobalVariable.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyIvarName.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyIvarValue.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyIvarVariable.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyTempName.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyTempNewValue.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variablenodes/testReifyTempValue.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalName.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalValue.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalVariable.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalVariableName.st A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalVariableValue.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarName.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarValue.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarVariable.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempName.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempNewValue.st R Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempValue.st M Reflectivity.package/HookGenerator.class/definition.st M Reflectivity.package/HookGenerator.class/instance/private/genReification_for_.st A Reflectivity.package/HookGeneratorForVariables.class/README.md A Reflectivity.package/HookGeneratorForVariables.class/definition.st M Reflectivity.package/RFNameReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFNameReification.class/instance/generate/genForLiteralVariable.st A Reflectivity.package/RFReification.class/instance/generate/genForClassVariable.st A Reflectivity.package/RFReification.class/instance/generate/genForLiteralVariable.st A Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/analyseForLinksForNodes_.st A Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/analyseForLinksForVariables_.st A Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/analyseForLinks_generator_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitMethodNode_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitNode_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitVarWrite_.st M Reflectivity.package/RFSemanticAnalyzer.class/instance/visiting/visitVariableNode_.st M Reflectivity.package/RFValueReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFValueReification.class/instance/generate/genForLiteralVariable.st M Reflectivity.package/RFValueReification.class/instance/generate/preamble_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50341.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50342.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50341.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50342.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50342 16640 Reflectivity: add support for reifications #name and #value for Class Variables https://pharo.fogbugz.com/f/cases/16640 http://files.pharo.org/image/50/50342.zip

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

2015-09-25 11:01 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : >> >>> >>> >>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com >>> <mailto:i.uhnak@gmail.com>>: >>> >>> > - 250 * 1.5 returns -2.25 >>> >>> why is this valid syntax? >>> >>> >>> >>> I don't know if this is valid syntax (I always wondered that there is >>> one place in PointTest, that is not compilable with old compiler but >>> compiles >>> fine with opal). >>> But the error happens in >>> RBParser>>#parseNegatedNumber. >>> If a #- is recognized, it tests if a literalnumber follows (but from the >>> token stream, that is, the spaces are ignored). >>> Now the real bug is, that we do two "steps" and concstruct a new >>> literalvaluenode from the now following tokens. >>> RBParser parseExpression:'- 2' -> throws an error, because no following >>> tokens >>> RBParser parseExpression:'- 2 * 3' -> works but actually duplicates the >>> two last tokens "*3 *3. >>> and some funny other things '- 2@1' -> '-1@1' >>> >> >> Another one I found in the tests: would you expect >> >> RBParser parseExpression: '# >> >> 1 = 1' >> >> To be the same thing as '#1 = 1' ? >> > > > And another one: > #t = ##t "-> true" > > I thnk ##t should be allowed. > I would allow it if it doesn't impact the code. At the moment, what I see is that ## is allowed because #scanLiteral is recursive for symbols... sort of side effect of the current implementation. If correcting makes it non-recursive, I won't introduce a special check to allow ## and ### and ####. ## has a special meaning in some smalltalks (Dolphin?). Removing ## would make porting Dolphin code (SmaCC, for example) harder. Thierry > > > >> >> Thierry >> > >

Sept. 25, 2015

Re: [Pharo-dev] SHRBTextStyler and workspace/playground variables

by Andrei Chis

On Fri, Sep 25, 2015 at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-09-24 12:06 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> Hi, >> >> Currently SHRBTextStyler does not highlight variables in the playground. >> This could be added by extending SHRBTextStyler >>#resolveStyleFor: with >> >> workspace >> ifNotNil: [(workspace hasBindingOf: aVariableNode name) >> ifTrue: [^ #workspaceVar]]. >> > > Yes, I tried it already, but I couldn't get it to work. > I would like to have some way to add this to the semantic analyser step. > If the workspace is defined as a requestore scope, the variable analysis > should work the same way as if we actual "compile" the code. > I also think this would be a much nicer solution. I looked a bit at the how requestor scopes work but it's not that clear how to add the workspace as a scope. Cheers, Andrei > > >> >> Still this could cause some problems given how MorphicTextAdapter >> integrates Rubric. >> >> MorphicTextAdapter>>setEditingModeFor:withBehavior: can translate >> #beForCode from Spec to #beForSmalltalkScripting in Rubric. >> However for #beForSmalltalkScripting to work the model has to provide >> methods for managing bindings which MorphicTextAdapter does not. >> >> > This is really difficult, especially because the actual model is different > for Nautilus code panes and of course any spec based text/code model. > > >> Maybe there is another way to highlight variables in the playground. >> >> Cheers, >> Andrei >> > >

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Nicolai Hess

2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : > >> >> >> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>>: >> >> > - 250 * 1.5 returns -2.25 >> >> why is this valid syntax? >> >> >> >> I don't know if this is valid syntax (I always wondered that there is >> one place in PointTest, that is not compilable with old compiler but >> compiles >> fine with opal). >> But the error happens in >> RBParser>>#parseNegatedNumber. >> If a #- is recognized, it tests if a literalnumber follows (but from the >> token stream, that is, the spaces are ignored). >> Now the real bug is, that we do two "steps" and concstruct a new >> literalvaluenode from the now following tokens. >> RBParser parseExpression:'- 2' -> throws an error, because no following >> tokens >> RBParser parseExpression:'- 2 * 3' -> works but actually duplicates the >> two last tokens "*3 *3. >> and some funny other things '- 2@1' -> '-1@1' >> > > Another one I found in the tests: would you expect > > RBParser parseExpression: '# > > 1 = 1' > > To be the same thing as '#1 = 1' ? > And another one: #t = ##t "-> true" I thnk ##t should be allowed. > > Thierry >

Sept. 25, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50341 Home: https://github.com/pharo-project/pharo-core

Sept. 25, 2015

[pharo-project/pharo-core] c0bee2: 50341

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c0bee2ffe7bb27ff8be5d07a05e3ad5acb220b7b https://github.com/pharo-project/pharo-core/commit/c0bee2ffe7bb27ff8be5d07a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-25 (Fri, 25 Sep 2015) Changed paths: M Graphics-Tests.package/PointTest.class/instance/tests-geometry/testToIntersectsTo.st M Kernel-Tests.package/BehaviorTest.class/instance/tests/testBehaviorRespectsPolymorphismWithTraitBehavior.st M OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta-data - dependency analyser/ignoredDependencies.st M OpalCompiler-Core.package/ManifestOpalCompilerCore.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/findVariable_ifNone_.st A OpalCompiler-Core.package/OCClassScope.class/instance/lookup/findVariable_ifNone_.st A OpalCompiler-Core.package/OCInstanceScope.class/instance/lookup/findVariable_ifNone_.st A OpalCompiler-Core.package/extension/SystemDictionary/instance/findVariable_ifNone_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50340.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50341.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50340.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50341.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/AbstractClassModification.class/instance/accessing/classLayout.st A Slot.package/AbstractClassModification.class/instance/accessing/classLayout_.st A Slot.package/extension/Behavior/instance/classLayout.st A Slot.package/extension/Behavior/instance/classLayout_.st R TxText-Styler.package/extension/OCAbstractMethodScope/instance/findVariable_ifNone_.st R TxText-Styler.package/extension/OCClassScope/instance/findVariable_ifNone_.st R TxText-Styler.package/extension/OCInstanceScope/instance/findVariable_ifNone_.st R TxText-Styler.package/extension/SystemDictionary/instance/findVariable_ifNone_.st Log Message: ----------- 50341 16591 #findVariable:ifNone: methods needs to go back to Opal https://pharo.fogbugz.com/f/cases/16591 16633 Rename layout to classLayout (step 1 add accessor) https://pharo.fogbugz.com/f/cases/16633 16639 fix non common smalltalk syntax in PointTest https://pharo.fogbugz.com/f/cases/16639 http://files.pharo.org/image/50/50341.zip

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

2015-09-25 9:53 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Note for ref on the original point: > > ANSI Smalltalk allow for space between - and the number token. Squeak is > then non A > > For the new point: > > ANSI Smalltalk does not allow for space between # and the selector, or > between # and the quoted string. > > Should be an easy fix. > Note to self for later: RBScanner>>#scanLiteral call stripSeparators before checking $# and calling again scanLiteral, which means it has a good chance of calling stripSeparators twice when dealing with the beginning of a symbol. Thierry > Marcus, how do we should validate RBParser changes? Reparse all the code > in the image and compares ASTs? > > Thierry > > > 2015-09-25 8:52 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > >> >> >> 2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> >>> Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : >>> >>>> >>>> >>>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com >>>> <mailto:i.uhnak@gmail.com>>: >>>> >>>> > - 250 * 1.5 returns -2.25 >>>> >>>> why is this valid syntax? >>>> >>>> >>>> >>>> I don't know if this is valid syntax (I always wondered that there is >>>> one place in PointTest, that is not compilable with old compiler but >>>> compiles >>>> fine with opal). >>>> But the error happens in >>>> RBParser>>#parseNegatedNumber. >>>> If a #- is recognized, it tests if a literalnumber follows (but from the >>>> token stream, that is, the spaces are ignored). >>>> Now the real bug is, that we do two "steps" and concstruct a new >>>> literalvaluenode from the now following tokens. >>>> RBParser parseExpression:'- 2' -> throws an error, because no following >>>> tokens >>>> RBParser parseExpression:'- 2 * 3' -> works but actually duplicates the >>>> two last tokens "*3 *3. >>>> and some funny other things '- 2@1' -> '-1@1' >>>> >>> >>> Another one I found in the tests: would you expect >>> >>> RBParser parseExpression: '# >>> >>> 1 = 1' >>> >>> To be the same thing as '#1 = 1' ? >>> >> >> I tested this in squeak and it seems that >> #1 isn't allowed as symbol, the only way to use a digit as symbol is >> #'1' (is this defined in smalltalks syntax defintion?) >> >> -> Parsing '#' has to be fixed too. >> >> >> >> >>> >>> Thierry >>> >> >> >

Sept. 25, 2015

Re: [Pharo-dev] [Reflectivity] What are the #arguments?

by roberto.minelli＠usi.ch

Thank you very much, Marcus! Concerning the table..we can do a method that lists the #availableReifications or something like that ;) For example, if I am interested in all the available reifications for an RBMethodNode I can do: RFReification subclasses select: [ :e | e nodes includesAny: RBMethodNode withAllSuperclasses ]. Cheers, Roby > On 25 Sep 2015, at 09:51, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > every one of these âreificationsâ are defined as a subclass of > RFReification > > There is one subclass for every symbol (e.g. for #arguments, there is RFArgumentsReification). > The class side method #key defines the exact symbol, while #nodes returns the AST node classes > where this reification is available. > > I will make a full table soon that lists everything. > > Marcus > >> On 25 Sep 2015, at 09:36, roberto.minelli(a)usi.ch wrote: >> >> Dear Marcus, >> >> I am wondering where to âdiscoverâ all the possible values for the #arguments: to pass to the MetaLink. >> >> Cheers, >> R >> >

Sept. 25, 2015

Re: [Pharo-dev] - 250 * 1.5 is not the same as 250 * 1.5

by Thierry Goubier

Note for ref on the original point: ANSI Smalltalk allow for space between - and the number token. Squeak is then non A For the new point: ANSI Smalltalk does not allow for space between # and the selector, or between # and the quoted string. Should be an easy fix. Marcus, how do we should validate RBParser changes? Reparse all the code in the image and compares ASTs? Thierry 2015-09-25 8:52 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-09-24 22:39 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> Le 24/09/2015 09:11, Nicolai Hess a Ã©crit : >> >>> >>> >>> 2015-09-24 8:19 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com >>> <mailto:i.uhnak@gmail.com>>: >>> >>> > - 250 * 1.5 returns -2.25 >>> >>> why is this valid syntax? >>> >>> >>> >>> I don't know if this is valid syntax (I always wondered that there is >>> one place in PointTest, that is not compilable with old compiler but >>> compiles >>> fine with opal). >>> But the error happens in >>> RBParser>>#parseNegatedNumber. >>> If a #- is recognized, it tests if a literalnumber follows (but from the >>> token stream, that is, the spaces are ignored). >>> Now the real bug is, that we do two "steps" and concstruct a new >>> literalvaluenode from the now following tokens. >>> RBParser parseExpression:'- 2' -> throws an error, because no following >>> tokens >>> RBParser parseExpression:'- 2 * 3' -> works but actually duplicates the >>> two last tokens "*3 *3. >>> and some funny other things '- 2@1' -> '-1@1' >>> >> >> Another one I found in the tests: would you expect >> >> RBParser parseExpression: '# >> >> 1 = 1' >> >> To be the same thing as '#1 = 1' ? >> > > I tested this in squeak and it seems that > #1 isn't allowed as symbol, the only way to use a digit as symbol is > #'1' (is this defined in smalltalks syntax defintion?) > > -> Parsing '#' has to be fixed too. > > > > >> >> Thierry >> > >

Sept. 25, 2015