January 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] New book for Pharo :)

by Casimiro de Almeida Barreto

I second that: you never fail to impress. Excellent work, Steph !!! On 29-01-2015 14:55, blake wrote: > You never fail to impress, Steph. Excellent work. > > On Wed, Jan 28, 2015 at 9:21 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Didier Besset offered his great book "Object-Oriented > Implementation of Numerical Methods > An Introduction with Smalltalk and Java" to the community. > (...) -- The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions. == This email may be signed using PGP key *ID: 1455478743A83CC3*

Jan. 31, 2015

Re: [Pharo-users] SmaCC: First steps

by kilon alios

thank for your congratulations, because at times I fear I ask too obvious questions. I have to say I find this parsing very complex but very fascinating too :) Time to experiment with the visitor. On Fri, Jan 30, 2015 at 11:49 PM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > > > 2015-01-30 14:04 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > >> Ok thanks for the info, I am still however curious about these "tests" >> are just tests (which may or may not happen) that determine the AST, for >> example which node to use ? >> > > 'tests' is just there because, in the grammar, there is this at a certain > point: > > testlist: > test 'test' "," testlist > | test 'test' comma_opt > ; > > I have named this use of test 'test', so SmaCC has deduced that testlist > will be a list of test(s) nodes (or maybe other stuff such as atoms, > depending on the productions for test).. so, SmaCC, in each rule where > testlist is found, it will add a 'tests' instance variable. > > So, basically, the grammar rules explain how each node can be decomposed > in sub-nodes, and the additional annotations (the 'test' naming and the > {{}} or {{}}) drive how the classes for the nodes you want to keep are > generated. In that testlist case, no node will be generated, but everywhere > testlist appear on the right of the rule, then it will add a 'tests' > instance variable. > > >> >> Or are they tests related to unit testing class PythonParserTests ? >> > > Not at all :) > > >> >> Also you said I need to use the visitor created by PythonParser I assume >> you mean PyRootNodeVisitor ? Just as it is explained in the AST chapter of >> the documentation. >> >> In my case this simple python list will need me to subclass it and >> override method visitListmaker , the aListmaker passed as argument to the >> method should I assume it is PyListmakerNode ? >> > > In my experience, what you need to do is you have a look at the ast > generated and see if you can recognize the elements. From what I see in > your simple example, the key to your list is that PyAtomNode instance with > something in list. Once you have that, you know that you need to visit > PyAtomNode (and check that it has the [ ] tokens). > > Looking into what is listmaker in atom in the grammar (congratulations by > the way, you have seen it :) ), you'll see that it creates a listmaker node > only in the first case: test followed by a list_for, otherwise it falls > back to testlist... > > Thierry > > > >> >> On Fri, Jan 30, 2015 at 10:50 AM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> Hi kilon, >>> >>> The tests instance variable is linked to the python grammar: top level >>> items in an expression are probably tests, and, through the grammar, tests >>> can be just atoms. >>> >>> So the tests instance variable doesn't means it is testing anything :) >>> >>> Thierry >>> Le 30 janv. 2015 09:23, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : >>> >>> Ok so I tried to parse a very simple list like >>>> >>>> [ 67,12342,5 ] >>>> >>>> using Parse and explore , I can find these number by following this AST >>>> (for example 67) >>>> >>>> PyFileInputNode>>statements: -> 1: PySimpleStmNode>>stmts: -> 1: >>>> PyExprStmtNode>>tests: ->1: PyPowerNode>>atom: -> PyAtomNode>>list: -> 1: >>>> PyPowerNode>>atom: -> PyPowerNode>>numberToken -> numberToken>>value -> 67 >>>> >>>> quite a structure, but the one thing I dont get is "tests" , why >>>> "tests" ? >>>> >>>> Does it tests something and if yes what ? >>>> >>> >> >

Jan. 30, 2015

Re: [Pharo-users] SmaCC: First steps

by Thierry Goubier

2015-01-30 14:04 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > Ok thanks for the info, I am still however curious about these "tests" are > just tests (which may or may not happen) that determine the AST, for > example which node to use ? > 'tests' is just there because, in the grammar, there is this at a certain point: testlist: test 'test' "," testlist | test 'test' comma_opt ; I have named this use of test 'test', so SmaCC has deduced that testlist will be a list of test(s) nodes (or maybe other stuff such as atoms, depending on the productions for test).. so, SmaCC, in each rule where testlist is found, it will add a 'tests' instance variable. So, basically, the grammar rules explain how each node can be decomposed in sub-nodes, and the additional annotations (the 'test' naming and the {{}} or {{}}) drive how the classes for the nodes you want to keep are generated. In that testlist case, no node will be generated, but everywhere testlist appear on the right of the rule, then it will add a 'tests' instance variable. > > Or are they tests related to unit testing class PythonParserTests ? > Not at all :) > > Also you said I need to use the visitor created by PythonParser I assume > you mean PyRootNodeVisitor ? Just as it is explained in the AST chapter of > the documentation. > > In my case this simple python list will need me to subclass it and > override method visitListmaker , the aListmaker passed as argument to the > method should I assume it is PyListmakerNode ? > In my experience, what you need to do is you have a look at the ast generated and see if you can recognize the elements. From what I see in your simple example, the key to your list is that PyAtomNode instance with something in list. Once you have that, you know that you need to visit PyAtomNode (and check that it has the [ ] tokens). Looking into what is listmaker in atom in the grammar (congratulations by the way, you have seen it :) ), you'll see that it creates a listmaker node only in the first case: test followed by a list_for, otherwise it falls back to testlist... Thierry > > On Fri, Jan 30, 2015 at 10:50 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi kilon, >> >> The tests instance variable is linked to the python grammar: top level >> items in an expression are probably tests, and, through the grammar, tests >> can be just atoms. >> >> So the tests instance variable doesn't means it is testing anything :) >> >> Thierry >> Le 30 janv. 2015 09:23, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : >> >> Ok so I tried to parse a very simple list like >>> >>> [ 67,12342,5 ] >>> >>> using Parse and explore , I can find these number by following this AST >>> (for example 67) >>> >>> PyFileInputNode>>statements: -> 1: PySimpleStmNode>>stmts: -> 1: >>> PyExprStmtNode>>tests: ->1: PyPowerNode>>atom: -> PyAtomNode>>list: -> 1: >>> PyPowerNode>>atom: -> PyPowerNode>>numberToken -> numberToken>>value -> 67 >>> >>> quite a structure, but the one thing I dont get is "tests" , why "tests" >>> ? >>> >>> Does it tests something and if yes what ? >>> >> >

Jan. 30, 2015

Re: [Pharo-users] how to debug zinc server errors from tests

by Sven Van Caekenberghe

> On 30 Jan 2015, at 10:11, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > > Excerpts from Sven Van Caekenberghe's message of 2015-01-30 07:59:00 +0100: >>> when debugging a zinc server with tests structured as in >>> http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/ >>> i am wondering how to best debug errors in the server while running tests. >>> >>> one test makes a ZnClient connection to a testserver started from the same test. >>> the test fails with the server returning a 500 error. >> Writing a unit test using both an HTTP client and server is already a bit >> tricky sometimes, having it fail is always ugly. This is more a threading >> issue than anything else. >> >> I usually will do as you describe: rerun manually with a server where debug is enabled. > > ok, unfortunately i now am facing an issue that i can not reproduce manually. i > suspect that is because of a difference between the test server (started in > withServerDo:) and my actual server. > > i could probably set up a clean image and retry it there. > how can i avoid that and run a clean server instance manually in my dev image? > >> It could be an idea to try to improve the situation, but it won't be easy. To >> enable a debug/continue style the client request should first not time out >> (which is not a good idea for unattended tests), then something should be >> done about the UI thread. > > well, i am glad they time out, otherwise i believe the image would be locked up. > the timeout should be paused though while the debugger is running. > > so the problem is really that the test would need to run in a separate thread > so as to not block the UI? but to do this, the whole test-running framework > would have to be changed, and it's not something i can do in the test code? There could be something wrong with your test itself. Why don't you post what you are doing ? > what about a hack to instead make a shorter timeout? let the test fail > immediately, then the UI can bring up the debugger, i can inspect the issue, > fix it and rerun the test? > > greetings, martin. > > -- > eKita - the online platform for your entire academic life > -- > chief engineer eKita.co > pike programmer pike.lysator.liu.se caudium.net societyserver.org > secretary beijinglug.org > mentor fossasia.org > foresight developer foresightlinux.org realss.com > unix sysadmin > Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Jan. 30, 2015

Re: [Pharo-users] how to debug zinc server errors from tests

by Sven Van Caekenberghe

> On 30 Jan 2015, at 12:18, Ben Coman <btc(a)openInWorld.com> wrote: > > If there is a particular test you want to run outside of the test framework, essentially you reproduce TestCase>>runCase in the Workspace. > For example... > MyClassTest new setUp testMyTest Actually the proper usage is MyTestCase run: #testSelector or MyTestCase debug: #testSelector > and you can wrap that in a fork. > > cheers -ben > > On Fri, Jan 30, 2015 at 5:11 PM, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > Excerpts from Sven Van Caekenberghe's message of 2015-01-30 07:59:00 +0100: > > > when debugging a zinc server with tests structured as in > > > http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/ > > > i am wondering how to best debug errors in the server while running tests. > > > > > > one test makes a ZnClient connection to a testserver started from the same test. > > > the test fails with the server returning a 500 error. > > Writing a unit test using both an HTTP client and server is already a bit > > tricky sometimes, having it fail is always ugly. This is more a threading > > issue than anything else. > > > > I usually will do as you describe: rerun manually with a server where debug is enabled. > > ok, unfortunately i now am facing an issue that i can not reproduce manually. i > suspect that is because of a difference between the test server (started in > withServerDo:) and my actual server. > > i could probably set up a clean image and retry it there. > how can i avoid that and run a clean server instance manually in my dev image? > > > It could be an idea to try to improve the situation, but it won't be easy. To > > enable a debug/continue style the client request should first not time out > > (which is not a good idea for unattended tests), then something should be > > done about the UI thread. > > well, i am glad they time out, otherwise i believe the image would be locked up. > the timeout should be paused though while the debugger is running. > > so the problem is really that the test would need to run in a separate thread > so as to not block the UI? but to do this, the whole test-running framework > would have to be changed, and it's not something i can do in the test code? > > what about a hack to instead make a shorter timeout? let the test fail > immediately, then the UI can bring up the debugger, i can inspect the issue, > fix it and rerun the test? > > greetings, martin. > > -- > eKita - the online platform for your entire academic life > -- > chief engineer eKita.co > pike programmer pike.lysator.liu.se caudium.net societyserver.org > secretary beijinglug.org > mentor fossasia.org > foresight developer foresightlinux.org realss.com > unix sysadmin > Martin BÃ¤hr working in china http://societyserver.org/mbaehr/ > >

Jan. 30, 2015

Re: [Pharo-users] how to install all of ZincHTTPComponents?

by Sven Van Caekenberghe

Are you sure you understand how Metacello configurations and groups works ? You are misinterpreting what you see. Please read the class comment of ConfigurationOfZincHTTPComponents. You have to load (at least) the 'REST' group for what you want. > On 30 Jan 2015, at 11:23, Martin BÃ¤hr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > > Excerpts from stepharo's message of 2015-01-30 11:05:15 +0100: >>> Excerpts from Sven Van Caekenberghe's message of 2015-01-30 07:52:53 +0100: >>>> What exactly did you do ? >>>> Zinc has been in Pharo since 1.3. Loading it from its configuration load a newer version. That has always worked for me and other. >>> so you are saying, everything should already be loaded, and i should not need >>> to do anything, other than updating? >> Yes >> And use Pharo40. > > then where is the Zinc-REST package? > > can't find it in any image i try. > > greetings, martin. > > -- > eKita - the online platform for your entire academic life > -- > chief engineer eKita.co > pike programmer pike.lysator.liu.se caudium.net societyserver.org > secretary beijinglug.org > mentor fossasia.org > foresight developer foresightlinux.org realss.com > unix sysadmin > Martin BÃ¤hr working in china http://societyserver.org/mbaehr/ >

Jan. 30, 2015

Re: [Pharo-users] New book for Pharo :)

by Damien Pollet

Let me demo the release process to the other maintainers, then we'll see ;) On 30 January 2015 at 18:46, Werner Kassens <wkassens(a)libello.com> wrote: > Hi Damien, > useful info indeed, thanks. do you intend to do the same with the big > version? > werner > > > On 01/30/2015 05:45 PM, Damien Pollet wrote: > >> I did a proper release of the PDF book on Github: >> https://github.com/SquareBracketAssociates/NumericalMethods/releases >> > >

Jan. 30, 2015

Re: [Pharo-users] New book for Pharo :)

by Werner Kassens

Hi Damien, useful info indeed, thanks. do you intend to do the same with the big version? werner On 01/30/2015 05:45 PM, Damien Pollet wrote: > I did a proper release of the PDF book on Github: > https://github.com/SquareBracketAssociates/NumericalMethods/releases

Jan. 30, 2015

Re: [Pharo-users] New book for Pharo :)

by Damien Pollet

I did a proper release of the PDF book on Github: https://github.com/SquareBracketAssociates/NumericalMethods/releases Try the big green button there, or direct link to the PDF: https://github.com/SquareBracketAssociates/NumericalMethods/releases/downlo… <https://github.com/SquareBracketAssociates/NumericalMethods/releases/downlo…> Heads up: I'd like to remove build results from the source repo, so the links Stef sent earlier might become invalid. On 29 January 2015 at 18:32, Werner Kassens <wkassens(a)libello.com> wrote: > Hi Ben, > i also prefer SCI, although i have another reason <g>, it has less letters > than MATH and the letters are positioned nearer to each other on my > keyboard (good for my one-handed typing approach). SciTalk is a really nice > idea i agree. > werner > > > On 01/29/2015 04:19 PM, Ben Coman wrote: > >> MATH seems to constraining. SCI seems good. And I like that suggestion >> for SciTalk. >> > >

Jan. 30, 2015

Re: [Pharo-users] StartupPreferenceLoader in Pharo 4?

by Martin BÃ¤hr

Excerpts from Martin BÃ¤hr's message of 2015-01-30 17:05:17 +0100: > i was just about to explore the StartupLoader described here: > https://ci.inria.fr/pharo-contribution/view/Books/job/PharoHiddenTreasures/… > only to find that it is deprecated, and i can't find its replacement: StartupPreferenceLoader oh, i found it: StartupPreferencesLoader now i wonder what else in that documentation is changed... greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin BÃ¤hr working in china http://societyserver.org/mbaehr/

Jan. 30, 2015