January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by Michael Roberts

np, i will have a look this weekend. I don't know exactly how to create emphasis, but Text and TextStream look likely. Look at class references and you will get some examples. Also senders of asText (152!), and surrounding protocol. I don't know how you integrate these into the workspace though. I'm sure there is an example somewhere. cheers, Mike 2010/1/15 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Michael: I will put some welcome workspaces in the next PharoDev. I also > have the same problem with the English. > I would also like to put italics and bold, but I have no idea how to do it. > > If you want to check what I wrote, would be really cool as I plan to do the > next dev image during the weekend. > > If you are willing to do it: > > Gofer new > Â Â Â squeaksource: 'ImageForDevelopers'; > Â Â Â package: 'ImageForDevelopers-pharo'; > Â Â Â load. > > > And look for the class side methods of DEVImageWorkspaces !!! > > Thanks for any feedback. > > Mariano > > On Fri, Jan 15, 2010 at 10:18 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: >> >> hey this is really neat! >> >> I can offer you some corrections or perhaps suggestions for better >> phrasing. Â just my native 2p if it helps. >> >> As a general comment, i know it would be more work, if you could get >> some emphasis e.g bold, italics it would really make the expressions >> and names of classes or methods stand out. >> >> ---Welcome--- >> I suppose you have called me to learn Smalltalk. >> --> >> You must want me to help you learn Smalltalk! >> >> ---Doing vs printing--- >> You've just executed a Smalltalk instruction >> --> >> You've just executed a Smalltalk expression >> >> >> ---Doing vs printing 2--- >> It's a Do It which print the result >> --> >> It's a Do It which prints the result >> >> >> ---basic types numbers--- >> you know how to execute Smalltalk code >> --> >> you now know how to execute Smalltalk code >> >> ---basic types characters--- >> A Character can be instanciated >> --> >> A Character can be instantiated >> >> --basic types string--- >> Use single quotes to create a String instance >> --> >> Use single quotes to create a String. >> >> ---basic types dynamic array--- >> Dynamic Array are created at execution time: >> --> >> Dynamic Arrays are created at execution time: >> >> >> ---unary messages--- >> Unary messages have the following form: >> Â Â anObject aMethod name >> --> >> anObject aMethodName >> >> --keyword messages-- >> The message is between:and: sent to Number object >> --> >> The message is between:and: sent to the Number 4 >> >> ---message syntax: execution order--- >> Between similar messages, expressions are executed from left to right >> --> >> Between messages of similar precedence, expressions are executed from >> left to right >> >> ---parentheses--- >> Use parentheses to change order >> --> >> Use parentheses to change order of evaluation >> >> ---mathematical precedence--- >> A message does not know mathematical precedence. Simplicity has a price :) >> --> >> (rephrase ?) >> Traditional precedence rules from mathematics do not follow in >> Smalltalk. Â The simplicity has a price ;) >> It might surprise you that precedence rules you know from mathematics >> do not apply here. Â This has a price as you can see... >> >> ---conditionals--- >> Conditionals are just message sent to Boolean objects >> --> >> Conditionals are just messages sent to Boolean objects >> >> ---loops--- >> Loops are messages send to collections, high-level iterators >> --> >> Loops are messages sent to collections, high-level iterators >> >> ---iterators--- >> Here we want to print all the numbers of the Transcript (a console) >> --> >> Here we want to print all the numbers on the Transcript (a console) >> >> ---() vs []--- >> --> >> I know what you are trying to articulate here, but this page doesn't >> really work since your 'annotation' is not syntactic and therefore >> your learning style breaks. >> pehaps have a think about this slide >> >> cheers >> Mike >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

Re: [Pharo-project] FileStream Squeak harvested

by StÃ©phane Ducasse

ok I imagine that this is this change. Name: Monticello-nice.342 Author: nice Time: 27 December 2009, 9:03:54 am UUID: ead29222-29d3-421a-8d89-08d667014c1c Ancestors: Monticello-bf.341 change #findSnapshotWithVersionInfo: to silently ignore a missing ancestor rather than sending #snapshot to nil. This happens for example when merging Pharo/CollectionTests. Don't know if this is the good strategy though (maybe a notification could be signalled) + Cosmetic: move or remove a few temps inside closures

Jan. 15, 2010

Re: [Pharo-project] FileStream Squeak harvested

by StÃ©phane Ducasse

>>> >>>> thanks levente. >>>> >>>> Now since this can also help squeak people. The trunk does not contain the complete history so this breaks monticello >>>> then browsing history. In pharo we pay attention to get **all** the ancestor chain for such a kind of analysis. >>> >>> I don't get you. The trunk allows you to rebuild an image from 3.10.2 to the actual state, so it contains the complete history since 3.10.2. >> >> There is a huge difference between been able to build an image as a list of changes apply to the previous snapshot from >> apply the last version of package to the original image. We learned that the hard way doing 3.9. > > Indeed, noone wants the latter, because it limits the range of changes available. But I would pay to have that possibility (but it will not possible in Smalltalk since Smalltalk does not have a declarative model of execution). >> Now this was not my point. My point is that MC like to have all the ancestors when we use merge in the history panel. >> if you click on File-ul.58.mcz then History you get the list with all the ancestors but some of them are not on the repository >> so you cannot view changes -> >> > > This is the bug I was talking about. It's a bug, since viewing the changes is indepentent of the ancestors. Ok then I will have a look. > >>> IIRC this MC bug has been fixed in the trunk. >> >> ok what is the logic to find that File.31 was the ancestor of File.47? > > MC shows you the ancestors of the currently loaded package (normal style, no undelines, not bold). There's also the history button which shows all ancestors with their commit messages, UUIDs, etc. > > > Levente > >> If this is the just to take the next matching number I prefer to get a pop up saying that 46 is not found. >> Because MC is a distributed version system so you should not take the hypothesis that all the versions are in the same >> repository. So I'm curious to know if we talk about the same. >> >> Stef >>> >>>> >>>> Stef >>>> >>>> On Jan 15, 2010, at 7:14 PM, Levente Uzonyi wrote: >>>> >>>>> On Fri, 15 Jan 2010, Mariano Martinez Peck wrote: >>>>> >>>>>> Hi: Today Stef and I have being harvested Squeak changes in FileStream. The >>>>>> most important is the work from Levente and the buffer. >>>>>> >>>>>> We commit the first slide in inbox: SLICE-FileStream-StephaneDucasse.1 >>>>>> >>>>>> Can someone take a look please because is this quite "important" to >>>>>> integrate. >>>>> >>>>> StandardFileStream >> #readInto:startingAt:count: is wrong, there's a >>>>> newer version. StandardFileStream >> #skip: is missing. >>>>> The changes for MultiByteFileStream are also missing. Without those, the >>>>> files' state may become corrupt and the expected system-wide speedup will >>>>> be less significant. >>>>> Changes of classes other than StandardFileStream are unrelated to the read >>>>> buffering in the slice. >>>>> >>>>> >>>>> Levente >>>>> >>>>>> >>>>>> Thanks >>>>>> >>>>>> Mariano >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 15, 2010

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by Mariano Martinez Peck

Michael: I will put some welcome workspaces in the next PharoDev. I also have the same problem with the English. I would also like to put italics and bold, but I have no idea how to do it. If you want to check what I wrote, would be really cool as I plan to do the next dev image during the weekend. If you are willing to do it: Gofer new squeaksource: 'ImageForDevelopers'; package: 'ImageForDevelopers-pharo'; load. And look for the class side methods of DEVImageWorkspaces !!! Thanks for any feedback. Mariano On Fri, Jan 15, 2010 at 10:18 PM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > hey this is really neat! > > I can offer you some corrections or perhaps suggestions for better > phrasing. just my native 2p if it helps. > > As a general comment, i know it would be more work, if you could get > some emphasis e.g bold, italics it would really make the expressions > and names of classes or methods stand out. > > ---Welcome--- > I suppose you have called me to learn Smalltalk. > --> > You must want me to help you learn Smalltalk! > > ---Doing vs printing--- > You've just executed a Smalltalk instruction > --> > You've just executed a Smalltalk expression > > > ---Doing vs printing 2--- > It's a Do It which print the result > --> > It's a Do It which prints the result > > > ---basic types numbers--- > you know how to execute Smalltalk code > --> > you now know how to execute Smalltalk code > > ---basic types characters--- > A Character can be instanciated > --> > A Character can be instantiated > > --basic types string--- > Use single quotes to create a String instance > --> > Use single quotes to create a String. > > ---basic types dynamic array--- > Dynamic Array are created at execution time: > --> > Dynamic Arrays are created at execution time: > > > ---unary messages--- > Unary messages have the following form: > anObject aMethod name > --> > anObject aMethodName > > --keyword messages-- > The message is between:and: sent to Number object > --> > The message is between:and: sent to the Number 4 > > ---message syntax: execution order--- > Between similar messages, expressions are executed from left to right > --> > Between messages of similar precedence, expressions are executed from > left to right > > ---parentheses--- > Use parentheses to change order > --> > Use parentheses to change order of evaluation > > ---mathematical precedence--- > A message does not know mathematical precedence. Simplicity has a price :) > --> > (rephrase ?) > Traditional precedence rules from mathematics do not follow in > Smalltalk. The simplicity has a price ;) > It might surprise you that precedence rules you know from mathematics > do not apply here. This has a price as you can see... > > ---conditionals--- > Conditionals are just message sent to Boolean objects > --> > Conditionals are just messages sent to Boolean objects > > ---loops--- > Loops are messages send to collections, high-level iterators > --> > Loops are messages sent to collections, high-level iterators > > ---iterators--- > Here we want to print all the numbers of the Transcript (a console) > --> > Here we want to print all the numbers on the Transcript (a console) > > ---() vs []--- > --> > I know what you are trying to articulate here, but this page doesn't > really work since your 'annotation' is not syntactic and therefore > your learning style breaks. > pehaps have a think about this slide > > cheers > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

Re: [Pharo-project] FileStream Squeak harvested

by StÃ©phane Ducasse

>> > > I find MC a bit pedantic sometimes. > I think this happens when we merged a private version somewhere on > someone disk with a trunk version then published. MC keep track of the > merged private version and insist on having this branch when we > further merge in Pharo. > FYI, exactly the same happened to me when I tried to merge some Pharo > version in squeak (an obscure DamienCassou branch was missing in pharo > repository, can't remember which package though...). Instead of > complaining instructively, MC was sending snapshot to nil... I just > let it ignore the problem. In Pharo, you choosed to signal the problem > with an explicit message, maybe that help fixing wrong configurations, > but sometimes you should just have the option to ignore and proceed. sure now I do not know what is the semantics of proceed. is it stop? Stef

Jan. 15, 2010

Re: [Pharo-project] FileStream Squeak harvested

by Levente Uzonyi

On Fri, 15 Jan 2010, StÃ©phane Ducasse wrote: > > On Jan 15, 2010, at 9:50 PM, Levente Uzonyi wrote: > >> On Fri, 15 Jan 2010, StÃ©phane Ducasse wrote: >> >>> thanks levente. >>> >>> Now since this can also help squeak people. The trunk does not contain the complete history so this breaks monticello >>> then browsing history. In pharo we pay attention to get **all** the ancestor chain for such a kind of analysis. >> >> I don't get you. The trunk allows you to rebuild an image from 3.10.2 to the actual state, so it contains the complete history since 3.10.2. > > There is a huge difference between been able to build an image as a list of changes apply to the previous snapshot from > apply the last version of package to the original image. We learned that the hard way doing 3.9. Indeed, noone wants the latter, because it limits the range of changes available. > > Now this was not my point. My point is that MC like to have all the ancestors when we use merge in the history panel. > if you click on File-ul.58.mcz then History you get the list with all the ancestors but some of them are not on the repository > so you cannot view changes -> > This is the bug I was talking about. It's a bug, since viewing the changes is indepentent of the ancestors. >> IIRC this MC bug has been fixed in the trunk. > > ok what is the logic to find that File.31 was the ancestor of File.47? MC shows you the ancestors of the currently loaded package (normal style, no undelines, not bold). There's also the history button which shows all ancestors with their commit messages, UUIDs, etc. Levente > If this is the just to take the next matching number I prefer to get a pop up saying that 46 is not found. > Because MC is a distributed version system so you should not take the hypothesis that all the versions are in the same > repository. So I'm curious to know if we talk about the same. > > Stef >> >>> >>> Stef >>> >>> On Jan 15, 2010, at 7:14 PM, Levente Uzonyi wrote: >>> >>>> On Fri, 15 Jan 2010, Mariano Martinez Peck wrote: >>>> >>>>> Hi: Today Stef and I have being harvested Squeak changes in FileStream. The >>>>> most important is the work from Levente and the buffer. >>>>> >>>>> We commit the first slide in inbox: SLICE-FileStream-StephaneDucasse.1 >>>>> >>>>> Can someone take a look please because is this quite "important" to >>>>> integrate. >>>> >>>> StandardFileStream >> #readInto:startingAt:count: is wrong, there's a >>>> newer version. StandardFileStream >> #skip: is missing. >>>> The changes for MultiByteFileStream are also missing. Without those, the >>>> files' state may become corrupt and the expected system-wide speedup will >>>> be less significant. >>>> Changes of classes other than StandardFileStream are unrelated to the read >>>> buffering in the slice. >>>> >>>> >>>> Levente >>>> >>>>> >>>>> Thanks >>>>> >>>>> Mariano >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

[Pharo-project] mac vm version number on pharo-project.org/pharo-download page

by John M McIntosh

I noticed the mac vm version number on pharo-project.org/pharo-download page is wrong, it says 4.2.2b2 but actually it's 4.2.2b1 If someone can correct it, that would be great and it will keep me from thinking I've managed to misplace a VM somewhere... -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 15, 2010

Re: [Pharo-project] VB-Regex News

by Lukas Renggli

There is an entry here: <http://code.google.com/p/pharo/issues/detail?id=1747>. And I committed it to the PharoInbox. Lukas 2010/1/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > excellent > lukas can you add an entry in the bugtracker. :) > Stef > >> Gofer new >> Â Â Â renggli: 'unsorted'; >> Â Â Â package: 'VB-Regex'; >> Â Â Â load >> >> - The VB-Regex engine has 160 new SUnit tests that cover 88% of the >> code-base. A few tests I wrote myself, but most of it comes from the >> class-side of RxParser that had an ad-hock test suite that painfully >> logged its results to the transcript. >> >> - I fixed the issue with the duplicated matches that was reported here >> <http://code.google.com/p/pharo/issues/detail?id=1747>. Unfortunately >> Vassili Bykov did not answer my questions. The fix is quite ugly and I >> had to rewrite most of the logic in RxMatcher. The test pass, but >> there might be new bugs. >> >> - The bad news is that matching is roughly 7% slower. I guess that's >> the price to pay for correct results. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 15, 2010

Re: [Pharo-project] VB-Regex News

by StÃ©phane Ducasse

excellent lukas can you add an entry in the bugtracker. :) Stef > Gofer new > renggli: 'unsorted'; > package: 'VB-Regex'; > load > > - The VB-Regex engine has 160 new SUnit tests that cover 88% of the > code-base. A few tests I wrote myself, but most of it comes from the > class-side of RxParser that had an ad-hock test suite that painfully > logged its results to the transcript. > > - I fixed the issue with the duplicated matches that was reported here > <http://code.google.com/p/pharo/issues/detail?id=1747>. Unfortunately > Vassili Bykov did not answer my questions. The fix is quite ugly and I > had to rewrite most of the logic in RxMatcher. The test pass, but > there might be new bugs. > > - The bad news is that matching is roughly 7% slower. I guess that's > the price to pay for correct results. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 15, 2010

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by Michael Roberts

hey this is really neat! I can offer you some corrections or perhaps suggestions for better phrasing. just my native 2p if it helps. As a general comment, i know it would be more work, if you could get some emphasis e.g bold, italics it would really make the expressions and names of classes or methods stand out. ---Welcome--- I suppose you have called me to learn Smalltalk. --> You must want me to help you learn Smalltalk! ---Doing vs printing--- You've just executed a Smalltalk instruction --> You've just executed a Smalltalk expression ---Doing vs printing 2--- It's a Do It which print the result --> It's a Do It which prints the result ---basic types numbers--- you know how to execute Smalltalk code --> you now know how to execute Smalltalk code ---basic types characters--- A Character can be instanciated --> A Character can be instantiated --basic types string--- Use single quotes to create a String instance --> Use single quotes to create a String. ---basic types dynamic array--- Dynamic Array are created at execution time: --> Dynamic Arrays are created at execution time: ---unary messages--- Unary messages have the following form: anObject aMethod name --> anObject aMethodName --keyword messages-- The message is between:and: sent to Number object --> The message is between:and: sent to the Number 4 ---message syntax: execution order--- Between similar messages, expressions are executed from left to right --> Between messages of similar precedence, expressions are executed from left to right ---parentheses--- Use parentheses to change order --> Use parentheses to change order of evaluation ---mathematical precedence--- A message does not know mathematical precedence. Simplicity has a price :) --> (rephrase ?) Traditional precedence rules from mathematics do not follow in Smalltalk. The simplicity has a price ;) It might surprise you that precedence rules you know from mathematics do not apply here. This has a price as you can see... ---conditionals--- Conditionals are just message sent to Boolean objects --> Conditionals are just messages sent to Boolean objects ---loops--- Loops are messages send to collections, high-level iterators --> Loops are messages sent to collections, high-level iterators ---iterators--- Here we want to print all the numbers of the Transcript (a console) --> Here we want to print all the numbers on the Transcript (a console) ---() vs []--- --> I know what you are trying to articulate here, but this page doesn't really work since your 'annotation' is not syntactic and therefore your learning style breaks. pehaps have a think about this slide cheers Mike

Jan. 15, 2010