May 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Saving a Smalltalk Project

by aglynn42＠gmail.com

Precision Systems in Houston specializes in finding/placing Smalltalk developers in the U.S. Andrew -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Brad Sent: Friday, May 4, 2018 1:15 PM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] Saving a Smalltalk Project Iâm a 20 year Smalltalker in Cleveland Ohio USA that would love to work another smalltalk project. It would have to be remote as Iâm unable to move due to family commitments, Brad Selfridge 913-269-2385 > On May 4, 2018, at 12:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > horrido <horrido.hobbies(a)gmail.com> wrote:. >> >> How hard would it be to find Smalltalkers willing to work in Silicon >> Valley, or South Africa? >> >> What is the best response to this person? Thanks. > > AFAIK it is not difficult at all to find Smalltalk developers. There > are lots of them here, on the other smalltalk mailing lists and on our Discord. > Pharo has a larger community, but HPI each year teaches Squeak to lots > (80?) of students. It should not be difficult at all to find > developers willing to work in Silicon Valley as long as youâd be able to afford them. > I assume they would be at least three times as expensive there as in > South Africa. The Smalltalkers youâll be able to find will most likely > be either just graduated or very experienced. > > Stephan > > >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Esteban A. Maringolo

On 04/05/2018 13:54, Richard Sargent wrote: >> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris <sean(a)clipperadams.com >> <mailto:sean@clipperadams.com>> wrote: >> >> Ramon Leon-5 wrote >> > And my point made; I don't even know what that means. >> >> Ha ha, I googled it and even after seeing the definition still didn't >> understand - we must be getting old ;-) > Also, if one Googles an acronym, such as the recently cited TMA, one > gets results like https://en.wikipedia.org/wiki/TMA (a disambiguation > page with a lengthy list). [I still don't know which TMA was meant, by > the way, so I can't use it for the following example.] If one Googles > Abstract Syntax Tree, one will find exactly what it means. But > additionally, one could make a reasonable guess at an approximation of > its meaning even without searching. I think that the "we have a TMA situation" is a nice joke if the right guess is that TMA means "Too Many Acronyms" :) Regards! -- Esteban A. Maringolo

May 4, 2018

Re: [Pharo-users] Mocketry: what is used of #where ?

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > > > Denis Kudriashov wrote: >> Hi Herbert. >> >> It is a bit experimental API to allow more descriptive failures. >> Evaluate following code: >> >> >> (2@3) where x should equal: 10 >> >> It will give you failure message: Got "2" from (2@3) x but it should >> equal "10". >> But without #where it would be: Got "2" but it should equal "10". >> >> And it works with long message chains: >> >> (2@3 corner: 10@30) where origin x should equal: 10 >> >> It will show: Got "2" from (2@3) corner: (10@30) origin x but it >> should equal "10". > > So in my case, I could see difference in something like this? > > responseCheck := (znClient > username: (self uidy: 'Q7') asString, '/TEST' password: > 'tk'; > timeout: 1; post; response) where. > responseCheck should be isSuccess. > responseCheck where contentType should equal: ZnMimeType > applicationJson. > responseCheck where entity should not be: nil. > > In that case it would be nice to be able to write something like: > > (znClient > username: (self uidy: 'Q7') asString, '/TEST' password: > 'tk'; > timeout: 1; post; response) where: [ :response | > response should be isSuccess. > response where contentType should equal: ZnMimeType > applicationJson. > response where entity should not be: nil ]. Ah, I get it, it prints the receiver and lists the message chain... ignore this. Thanks. >> I am still not sure is it good approach or not. But that is idea. >> Besides It is possible to retrieve such information using magic with >> thisContext and reflectivity. But again the question is same: does it >> really make sense to do it for assertions? >> >> Best regards, >> Denis >> >> >> >> 2018-05-04 16:28 GMT+03:00 Herbert VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>>: >> >> Hello, >> >> When I am writing tests using Mocketry's DSL, I get puzzled about >> how / when to use #where, and how is it different when it's used and >> when it is not? >> >> As far as i tried, I did not find any difference. That is, pasting >> part of one of my tests: >> >> response := znClient >> username: (self uidy: 'Q7') asString, '/TEST' >> password: 'tk'; >> timeout: 1; post; response. >> response should be isSuccess. >> response where contentType should equal: ZnMimeType >> applicationJson. >> response where entity should not be: nil. >> (STON fromString: response entity contents) should equal: >> nil >> >> I get the same result (pass if ok, failure with DNU when thing is >> not present) whether `where` is there or isn't. >> >> Could you explain what is it's purpose and correct usage? >> >> Thanks, Herby >> >> >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Richard Sargent

On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2018-05-04 19:45 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> Ramon Leon-5 wrote >> > And my point made; I don't even know what that means. >> >> Ha ha, I googled it and even after seeing the definition still didn't >> understand - we must be getting old ;-) >> >> Regarding the use of acronyms - while I agree with you as a general >> principle, I wonder about this case. Since the argument IIUC is that "a >> general user won't know the domain well enough to understand the acronym", >> would they understand "abstractSyntaxTree"?! > > > Now I am wonder: is it really correct to call syntax tree as abstract when > it is really implemented? > AST is very known term but now when I read it word by word I have such > questions :). > In computer science, an *abstract syntax tree* (AST), or just *syntax tree*, is a *tree* representation of the *abstract syntactic *structure of source code written in a programming language. [Wikipedia] > > >> That, to me, is as opaque as >> the acronym for one not acquainted with the domain, and may buy us little >> at >> the cost of a good amount of extra typing. Maybe keep the acronym and add >> a >> good method commentâ¦ >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

May 4, 2018

Re: [Pharo-users] Saving a Smalltalk Project

by Brad

Iâm a 20 year Smalltalker in Cleveland Ohio USA that would love to work another smalltalk project. It would have to be remote as Iâm unable to move due to family commitments, Brad Selfridge 913-269-2385 > On May 4, 2018, at 12:03 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > horrido <horrido.hobbies(a)gmail.com> wrote:. >> >> How hard would it be to find Smalltalkers willing to work in Silicon Valley, >> or South Africa? >> >> What is the best response to this person? Thanks. > > AFAIK it is not difficult at all to find Smalltalk developers. There are > lots of them here, on the other smalltalk mailing lists and on our Discord. > Pharo has a larger community, but HPI each year teaches Squeak to lots > (80?) of students. It should not be difficult at all to find developers > willing to work in Silicon Valley as long as youâd be able to afford them. > I assume they would be at least three times as expensive there as in South > Africa. The Smalltalkers youâll be able to find will most likely be either > just graduated or very experienced. > > Stephan > > >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Denis Kudriashov

2018-05-04 19:45 GMT+03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Ramon Leon-5 wrote > > And my point made; I don't even know what that means. > > Ha ha, I googled it and even after seeing the definition still didn't > understand - we must be getting old ;-) > > Regarding the use of acronyms - while I agree with you as a general > principle, I wonder about this case. Since the argument IIUC is that "a > general user won't know the domain well enough to understand the acronym", > would they understand "abstractSyntaxTree"?! Now I am wonder: is it really correct to call syntax tree as abstract when it is really implemented? AST is very known term but now when I read it word by word I have such questions :). > That, to me, is as opaque as > the acronym for one not acquainted with the domain, and may buy us little > at > the cost of a good amount of extra typing. Maybe keep the acronym and add a > good method commentâ¦ > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Richard Sargent

"Maybe keep the acronym and add a good method commentâ¦ " No. Please, really no. Do not use comments embedded *inside* methods to cover for naming the method badly. That is actually a counter-argument to using the acronym. Also, if one Googles an acronym, such as the recently cited TMA, one gets results like https://en.wikipedia.org/wiki/TMA (a disambiguation page with a lengthy list). [I still don't know which TMA was meant, by the way, so I can't use it for the following example.] If one Googles Abstract Syntax Tree, one will find exactly what it means. But additionally, one could make a reasonable guess at an approximation of its meaning even without searching. On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Ramon Leon-5 wrote > > And my point made; I don't even know what that means. > > Ha ha, I googled it and even after seeing the definition still didn't > understand - we must be getting old ;-) > > Regarding the use of acronyms - while I agree with you as a general > principle, I wonder about this case. Since the argument IIUC is that "a > general user won't know the domain well enough to understand the acronym", > would they understand "abstractSyntaxTree"?! That, to me, is as opaque as > the acronym for one not acquainted with the domain, and may buy us little > at > the cost of a good amount of extra typing. Maybe keep the acronym and add a > good method commentâ¦ > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Sean P. DeNigris

Ramon Leon-5 wrote > And my point made; I don't even know what that means. Ha ha, I googled it and even after seeing the definition still didn't understand - we must be getting old ;-) Regarding the use of acronyms - while I agree with you as a general principle, I wonder about this case. Since the argument IIUC is that "a general user won't know the domain well enough to understand the acronym", would they understand "abstractSyntaxTree"?! That, to me, is as opaque as the acronym for one not acquainted with the domain, and may buy us little at the cost of a good amount of extra typing. Maybe keep the acronym and add a good method commentâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 4, 2018

Re: [Pharo-users] Saving a Smalltalk Project

by Stephan Eggermont

horrido <horrido.hobbies(a)gmail.com> wrote:. > > How hard would it be to find Smalltalkers willing to work in Silicon Valley, > or South Africa? > > What is the best response to this person? Thanks. AFAIK it is not difficult at all to find Smalltalk developers. There are lots of them here, on the other smalltalk mailing lists and on our Discord. Pharo has a larger community, but HPI each year teaches Squeak to lots (80?) of students. It should not be difficult at all to find developers willing to work in Silicon Valley as long as youâd be able to afford them. I assume they would be at least three times as expensive there as in South Africa. The Smalltalkers youâll be able to find will most likely be either just graduated or very experienced. Stephan

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Ramon Leon

On 05/04/2018 01:29 AM, Ben Coman wrote: > a TMA situation? And my point made; I don't even know what that means. -- Ramon Leon

May 4, 2018