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

Re: [Pharo-dev] IceBerg and push for projects vs packages

by Serge Stinckwich

On Mon, Aug 29, 2016 at 2:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> On 29 Aug 2016, at 14:04, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> On Mon, Aug 29, 2016 at 10:52 AM, Nicolas Passerini >> <npasserini(a)gmail.com> wrote: >>> Well, I am not sure if this has to do with Iceberg itself, because Iceberg >>> does nothing with dependencies. >>> >>> But I am not sure that a ConfigurationOfXXX really has information of only >>> one package. Normally you will have only one configuration for each project, >>> am I wrong? >>> Then the configuration specifies (among other stuff) dependencies between >>> the parts (packages) of your project... I think this is right. >>> If you depend in another project, then you should not depend in specific >>> packages but in another configuration. >> >> With the Iceberg tool, you can load or unload packages. >> How it will works if the dependencies are not loaded before ? > > AFAIK, this is not iceberg concernâ¦ this is a work for metacello (or cargo). Yes you are right, but when you load a package from Iceberg, the dependencies should be loaded at the same time I guess. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 29, 2016

Re: [Pharo-dev] IceBerg and push for projects vs packages

by Esteban Lorenzano

> On 29 Aug 2016, at 14:04, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > On Mon, Aug 29, 2016 at 10:52 AM, Nicolas Passerini > <npasserini(a)gmail.com> wrote: >> Well, I am not sure if this has to do with Iceberg itself, because Iceberg >> does nothing with dependencies. >> >> But I am not sure that a ConfigurationOfXXX really has information of only >> one package. Normally you will have only one configuration for each project, >> am I wrong? >> Then the configuration specifies (among other stuff) dependencies between >> the parts (packages) of your project... I think this is right. >> If you depend in another project, then you should not depend in specific >> packages but in another configuration. > > With the Iceberg tool, you can load or unload packages. > How it will works if the dependencies are not loaded before ? AFAIK, this is not iceberg concernâ¦ this is a work for metacello (or cargo). Esteban > >> The problem here is that we are (at least Iceberg is) assuming a correlation >> between project and repository, because in fact Iceberg handles >> repositories. If a project would be spawn in several repositories, at least >> now Iceberg can't do anything about it, it will treat them as independent >> "projects". I am not sure about changing this logic in the near future, and >> also we should think if that is not a Cargo/Metacello feature. > > I never see a project spawn on many repo. I guess you can safely say > that 1 project = 1 repo. > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

Aug. 29, 2016

Re: [Pharo-dev] IceBerg and push for projects vs packages

by Serge Stinckwich

On Mon, Aug 29, 2016 at 10:52 AM, Nicolas Passerini <npasserini(a)gmail.com> wrote: > Well, I am not sure if this has to do with Iceberg itself, because Iceberg > does nothing with dependencies. > > But I am not sure that a ConfigurationOfXXX really has information of only > one package. Normally you will have only one configuration for each project, > am I wrong? > Then the configuration specifies (among other stuff) dependencies between > the parts (packages) of your project... I think this is right. > If you depend in another project, then you should not depend in specific > packages but in another configuration. With the Iceberg tool, you can load or unload packages. How it will works if the dependencies are not loaded before ? > The problem here is that we are (at least Iceberg is) assuming a correlation > between project and repository, because in fact Iceberg handles > repositories. If a project would be spawn in several repositories, at least > now Iceberg can't do anything about it, it will treat them as independent > "projects". I am not sure about changing this logic in the near future, and > also we should think if that is not a Cargo/Metacello feature. I never see a project spawn on many repo. I guess you can safely say that 1 project = 1 repo. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by Thierry Goubier

2016-08-29 11:42 GMT+02:00 stepharo <stepharo(a)free.fr>: > Thierry > > If you have a better editor control even better :) > What I did is yank that sort of behavior into independent commands that are keymap-bound to an editor. A lot easier to customize " independently of ', (, [. > > Syntax wise, one could consider "" to be inside a comment (i.e. do not > split into two comments if encountered inside a comment, as it is done now). > > This one could be nice too :) > And simple: probably just a line or two inside RBScanner. Thierry

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by Peter UhnÃ¡k

On Mon, Aug 29, 2016 at 11:42 AM, stepharo <stepharo(a)free.fr> wrote: > Thierry > > If you have a better editor control even better :) > > > Syntax wise, one could consider "" to be inside a comment (i.e. do not > split into two comments if encountered inside a comment, as it is done now). > > This one could be nice too :) > This would be also consistent with how single quotes are handled in a string, which would make it doublenice. :) Peter

Aug. 29, 2016

Re: [Pharo-dev] About the non-use of Announcer in Bloc

by Denis Kudriashov

Hi 2016-08-29 8:25 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Glenn, > > Thanks a lot for this experiment. Could you send us the code snippet so > people can play with it? > Or some links where to download image with Bloc-Tests

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by stepharo

Thierry If you have a better editor control even better :) > > Syntax wise, one could consider "" to be inside a comment (i.e. do not > split into two comments if encountered inside a comment, as it is done > now). This one could be nice too :)

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by Thierry Goubier

2016-08-29 10:58 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi Stef, > > 2016-08-29 8:35 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> This is a really nice and important question. >> I would really have a clear answer because it will make the system more >> stable. >> >> If you can build an analysis and let us know it would be really great. >> >> >> Something related but not on the same topic is that I would love to have >> a syntax for nested comments. >> >> This is really annoying to have to uncomment parts when we have to >> comment a large part. We discussed this back in 2007-2009 but we never did >> it. >> > > If your need is that (uncomment while commenting and the reverse), then > the answer is not a syntax change, but a better comment/uncomment command > in the editor. > > Now that you say that, I also have the issue. I'll have a try in > AltBrowser if I can get the behavior you'd like. > That works, but: - Single click select doesn't work very well (stops at the next double quotes instead of the end double quote) - The formatter likes to split double quotes (adding returns) - Backporting that to a standard editor is a mess, because there is a need to change the #enclose: method. Syntax wise, one could consider "" to be inside a comment (i.e. do not split into two comments if encountered inside a comment, as it is done now). Thierry > > Thierry > > >> >> >> Stef >> >> >> Le 28/8/16 Ã 12:17, Nicolai Hess a Ã©crit : >> >> Hi, >>> >>> where can I find a good reference about what characters are allowed as >>> binary selectors (from old syntax definition) and what is nowadays >>> allowed >>> by the implementations. >>> >>> And whether the current set of allowed binaries selector includes some >>> additions on >>> purpose or if this is just a bug of the parser. >>> >>> From what I found out, (Blue book and some other smalltalk syntax >>> definitions) >>> the current set of allowed characters includes the "special characters": >>> $! $% $& $* $+ $, $- $/ $< $= $> $? $@ $\ $| $~ >>> (some implementation do not allow $@ and some calls $- not a special >>> character >>> but allowed as binary selector character) >>> >>> And this is what String>>#numArgs uses. Therefore >>> >>> '-' numArgs "->1". >>> '!' numArgs "->1". >>> And for example: >>> 'Â§' numArgs "-> -1 (the -1 is indicating "not even a valid selector")" >>> >>> But I am interested in the characters not called "special characters and >>> not even in the range 0-126. >>> >>> The scanner allowes much more characters to be used as a selector name >>> (From the scanners typeTable) : >>> >>> {Character value: 1 . Character value: 2 . Character value: 3 . >>> Character value: 4 . Character value: 5 . Character value: 6 . Character >>> value: 7 . Character backspace . Character value: 11 . Character value: 14 >>> . Character value: 15 . Character value: 16 . Character value: 17 . >>> Character value: 18 . Character value: 19 . Character value: 20 . Character >>> value: 21 . Character value: 22 . Character value: 23 . Character value: 24 >>> . Character value: 25 . Character value: 26 . Character escape . Character >>> value: 28 . Character value: 29 . Character value: 30 . Character value: 31 >>> . $! . $% . $& . $* . $+ . $, . $- . $/ . $< . $= . $> . $? . $@ . $\ . $` >>> . $~ . Character delete . $â¬ . $ . $â . $Æ . $â . $â¦ . $â . $â¡ . $Ë . $â° . >>> $Å . $â¹ . $Å . $ . $Å½ . $ . $ . $â . $â . $â . $â . $â¢ . $â . $â . $Ë . $â¢ >>> . $Å¡ . $âº . $Å . $ . $Å¾ . $Å¸ . $ . $Â¡ . $Â¢ . $Â£ . $Â¤ . $Â¥ . $Â¦ . $Â§ . $Â¨ . >>> $Â© . $Â« . $Â¬ . $Â . $Â® . $Â¯ . $Â° . $Â± . $Â² . $Â³ . $Â´ . $Â¶ . $Â· . $Â¸ . $Â¹ . >>> $Â» . $Â¼ . $Â½ . $Â¾ . $Â¿ . $Ã . $Ã·} >>> >>> This means you can define a method with for example the name "Ã·". >>> >>> So , the question I want to ask. What do we want to allow as a binary >>> selector (character). >>> All that is nowadays "parseable" as binary selector, or only the set of >>> "special characters" >>> or something between both, and where to put this information, the "this >>> is an allowed binary >>> selector character" information? >>> >>> Thanks >>> Nicolai >>> >>> >> >> >

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by Nicolai Hess

2016-08-28 13:41 GMT+02:00 monty <monty2(a)programmer.net>: > See RBParserTest>>#testBinarySelectors > > It's based on the draft ANSI Smalltalk-80 standard. You integrated it. It > tests the RBParser's parsing of binary method definitions and message sends > of all binary selectors from 1 char upto 3 chars. (The Blue Book is more > restrictive than ANSI, limiting them to 2 chars max IIRC.) > > I wrote the test because of issues I had with the OldCompiler's handling > of selectors containing "|" and issues on other platforms like GemStone, so > the behavior I need and think is correct won't get broken without warning. > > Hi Monty, yes, but I am just wondering why the scanner interprets some characters as binary selector token, whereas they are not allowed as binary selectors. In the old scanner, the initialization of the type table just sets " binary token" as the default for all characters and changes some of them explicit to for example ($0 asciiValue to: $9 asciiValue) -> digit tokens #(9 10 12 13 32 ) -> delimiter token ... But RBScanner on the other hand explicitly sets some non-ascii characters to be used as "binary tokens" classificationTable at: 177 put: #binary. "plus-or-minus" classificationTable at: 183 put: #binary. "centered dot" classificationTable at: 215 put: #binary. "times" classificationTable at: 247 put: #binary. "divide" It looks like someone ( or somewhere ) it should be allowed to use these characters as a binary selector "#($Â± $Â· $Ã $Ã·)" Although later at the parsing step, using this tokens for binary message selectors isn't allowed. I think I will exclude these characters as binary selector tokens.

Aug. 29, 2016

Re: [Pharo-dev] Binary selector and special characters

by Thierry Goubier

Hi Stef, 2016-08-29 8:35 GMT+02:00 stepharo <stepharo(a)free.fr>: > This is a really nice and important question. > I would really have a clear answer because it will make the system more > stable. > > If you can build an analysis and let us know it would be really great. > > > Something related but not on the same topic is that I would love to have a > syntax for nested comments. > > This is really annoying to have to uncomment parts when we have to comment > a large part. We discussed this back in 2007-2009 but we never did it. > If your need is that (uncomment while commenting and the reverse), then the answer is not a syntax change, but a better comment/uncomment command in the editor. Now that you say that, I also have the issue. I'll have a try in AltBrowser if I can get the behavior you'd like. Thierry > > > Stef > > > Le 28/8/16 Ã 12:17, Nicolai Hess a Ã©crit : > > Hi, >> >> where can I find a good reference about what characters are allowed as >> binary selectors (from old syntax definition) and what is nowadays allowed >> by the implementations. >> >> And whether the current set of allowed binaries selector includes some >> additions on >> purpose or if this is just a bug of the parser. >> >> From what I found out, (Blue book and some other smalltalk syntax >> definitions) >> the current set of allowed characters includes the "special characters": >> $! $% $& $* $+ $, $- $/ $< $= $> $? $@ $\ $| $~ >> (some implementation do not allow $@ and some calls $- not a special >> character >> but allowed as binary selector character) >> >> And this is what String>>#numArgs uses. Therefore >> >> '-' numArgs "->1". >> '!' numArgs "->1". >> And for example: >> 'Â§' numArgs "-> -1 (the -1 is indicating "not even a valid selector")" >> >> But I am interested in the characters not called "special characters and >> not even in the range 0-126. >> >> The scanner allowes much more characters to be used as a selector name >> (From the scanners typeTable) : >> >> {Character value: 1 . Character value: 2 . Character value: 3 . Character >> value: 4 . Character value: 5 . Character value: 6 . Character value: 7 . >> Character backspace . Character value: 11 . Character value: 14 . Character >> value: 15 . Character value: 16 . Character value: 17 . Character value: 18 >> . Character value: 19 . Character value: 20 . Character value: 21 . >> Character value: 22 . Character value: 23 . Character value: 24 . Character >> value: 25 . Character value: 26 . Character escape . Character value: 28 . >> Character value: 29 . Character value: 30 . Character value: 31 . $! . $% . >> $& . $* . $+ . $, . $- . $/ . $< . $= . $> . $? . $@ . $\ . $` . $~ . >> Character delete . $â¬ . $ . $â . $Æ . $â . $â¦ . $â . $â¡ . $Ë . $â° . $Å . $â¹ >> . $Å . $ . $Å½ . $ . $ . $â . $â . $â . $â . $â¢ . $â . $â . $Ë . $â¢ . $Å¡ . >> $âº . $Å . $ . $Å¾ . $Å¸ . $ . $Â¡ . $Â¢ . $Â£ . $Â¤ . $Â¥ . $Â¦ . $Â§ . $Â¨ . $Â© . >> $Â« . $Â¬ . $Â . $Â® . $Â¯ . $Â° . $Â± . $Â² . $Â³ . $Â´ . $Â¶ . $Â· . $Â¸ . $Â¹ . $Â» . >> $Â¼ . $Â½ . $Â¾ . $Â¿ . $Ã . $Ã·} >> >> This means you can define a method with for example the name "Ã·". >> >> So , the question I want to ask. What do we want to allow as a binary >> selector (character). >> All that is nowadays "parseable" as binary selector, or only the set of >> "special characters" >> or something between both, and where to put this information, the "this >> is an allowed binary >> selector character" information? >> >> Thanks >> Nicolai >> >> > >

Aug. 29, 2016