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

[Thierry Goubier]

Le 04/05/2018 à 21:13, Denis Kudriashov a écrit :


2018-05-04 21:10 GMT+03:00 Richard Sargent 
>:


On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov
mailto:dionisi...@gmail.com>> wrote:


2018-05-04 19:45 GMT+03:00 Sean P. DeNigris
mailto:s...@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]


I know it. But my stupid question is why it's still called abstract 
while it is implemented for concrete language?


This is to make the difference between the parse tree (or concrete 
syntax tree) and the transformation of that parse tree into an abstract 
syntax tree (where a bunch of syntax tree nodes created by the parsing 
are removed or made absent... they are not needed to represent the code 
structure). Hence the abstract: the abstract syntax tree is an 
abstraction of the parse tree, even if it represent an exhaustive view 
of a concrete piece of code.


https://web.stanford.edu/class/archive/cs/cs143/cs143.1128/lectures/02/Slides02.pdf, 
slide 159 onward.



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

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

[Ben Coman]

On 5 May 2018 at 02:20, Esteban A. Maringolo  wrote:

>
> On 04/05/2018 13:54, Richard Sargent wrote:
>
> >> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris  >> > wrote:
> >>
> >> Ramon Leon-5 wrote
> >> > And my point made; I don't even know what that means.
>

Yes. Point made  ;)


> >>
> >> 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" :)


You got it !!

cheers -ben

[Pharo-users] [Job] Pharo developers wanted in Toronto

[Ben Coman]

On 4 May 2018 at 22:00,  wrote:

> Telna is looking for developers with Smalltalk experience, preferably
> Pharo,  in Toronto Canada.
>
> The role is listed on indeed.ca if anyone is interested.
>
> Andrew Glynn
>

Thanks Andrew.

Because people are generally interested in seeing where Pharo is being used,
I think there is value in copying here the whole job post for the mail
archives.
If we get to the point where there are too many such posts  actually
that would be a great outcome and we can review policy then.

Personally I find this usage very interesting...

cheers -ben

-
Telna is a global network operator that focuses on providing "out of the
box" connectivity to devices, machines, users and manufacturers. We are
changing the way networks operator, by focusing on scalable
software-defined networks that can be deployed anywhere in the world in
minutes rather than years.

We are looking for *Software Engineers* to join our network team to design
and develop the core tools that drive our "Network as a Service"
platform. *Development
experience in smalltalk is mandatory.*

This is a unique opportunity that will give the selected candidate(s) the
ability to learn about the operations of a mobile network and hands-on
experience developing the software systems that form the backbone of our
services.

*Mandatory Skills Required:*

   - *4+ years* of Smalltalk Development (Pharo preferred )
   - Strong understanding of Linux and databases (MongoDB, MySQL)

*Bonus Skills:*

   - Telecom experience

While a *Bachelors degree in Computer Science, Engineering* or related is
required, relevant experience will be taken into consideration.

Telna welcomes and encourages applications from people with disabilities.
Accommodations are available on request for candidates taking part in all
aspects of the selection process.

Job Type: Full-time

Experience:

   - Smalltalk Development: 4 years (Required)
   - Pharo development: 4 years (Preferred)

Education:

   - Bachelor's (Required)

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

[aglynn42]

Just as TLA is a three letter acronym ... 😊

-Original Message-
From: Pharo-users  On Behalf Of Esteban A. 
Maringolo
Sent: Friday, May 4, 2018 2:21 PM
To: Any question about pharo is welcome ; Richard 
Sargent 
Subject: Re: [Pharo-users] #ast vs. #parseTree


On 04/05/2018 13:54, Richard Sargent wrote:

>> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris 
>> mailto:s...@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

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

[Denis Kudriashov]

2018-05-04 21:10 GMT+03:00 Richard Sargent <
richard.sarg...@gemtalksystems.com>:

> On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov 
> wrote:
>
>>
>> 2018-05-04 19:45 GMT+03:00 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"?!
>>
>>
>> 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]
>

I know it. But my stupid question is why it's still called abstract while
it is implemented for concrete language?


>
>
>>
>>
>>> 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
>>>
>>>
>>
>

Re: [Pharo-users] Saving a Smalltalk Project

[aglynn42]

Precision Systems in Houston specializes in finding/placing Smalltalk 
developers in the U.S.

Andrew

-Original Message-
From: Pharo-users  On Behalf Of Brad
Sent: Friday, May 4, 2018 1:15 PM
To: Any question about pharo is welcome 
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  wrote:
> 
> horrido  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
> 
> 
> 

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

[Esteban A. Maringolo]

On 04/05/2018 13:54, Richard Sargent wrote:

>> On Fri, May 4, 2018 at 9:45 AM, Sean P. DeNigris > > 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

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

[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 >:


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

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

[Richard Sargent]

On Fri, May 4, 2018 at 1:04 PM, Denis Kudriashov 
wrote:

>
> 2018-05-04 19:45 GMT+03:00 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"?!
>
>
> 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
>>
>>
>

Re: [Pharo-users] Saving a Smalltalk Project

[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  wrote:
> 
> horrido  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
> 
> 
> 

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

[Denis Kudriashov]

2018-05-04 19:45 GMT+03:00 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"?!


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
>
>

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

[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 
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
>
>

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

[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

Re: [Pharo-users] Saving a Smalltalk Project

[Stephan Eggermont]

horrido  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

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

[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

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

[Herbert Vojčík]

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 ].


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 >:


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

Re: [Pharo-users] Saving a Smalltalk Project

[serge . stinckwich]

Arduinos&Raspberry boards + Lora radio board

Envoyé de mon iPhone

> Le 3 mai 2018 à 02:40, Todd Blanchard  a écrit :
> 
> OK, so I'm curious what hardware platforms you guys use for your "things"?
> 
> Been doing things with Particle lately.  Interested to try their new mesh 
> offering.
> 
>> On May 2, 2018, at 12:30 PM, Serge Stinckwich  
>> wrote:
>> 
>> If they are interested, we can get in touch. We are working on IoT for 
>> environmental monitoring and I’m working in Cameroon.
>> 
>> Regards,
>> 
>> Envoyé de mon iPad
>> 
>>> Le 2 mai 2018 à 19:21, horrido  a écrit :
>>> 
>>> I received the following message:
>>> 
>>> *We started off doing a small project in conservation in South Africa that
>>> involved tracking Rhinos in a remote GPS denied environment and ended up
>>> with some impressive building blocks for a Big Data Platform for IoT. The
>>> platform includes its own GIS subsystem and parts of an Expert System.
>>> 
>>> Due to the choice made by my business partner and handful of contractors the
>>> platform ended up being built in Smalltalk on Squeak  VM and the Magma
>>> Object Database.
>>> 
>>> We now believe we may have the beginning of a commercial platform however
>>> its notoriously difficult to find Smalltalk developers so I am in half minds
>>> to migrate to a platform which uses a more mainstream language (Java /
>>> Python) as I have been getting some strange reactions from Angel Investors /
>>> VCs and mainstream developers.
>>> 
>>> ...
>>> 
>>> I wanted to ask you if you have information on how big the Smalltalk
>>> community is and whether its better to migrate to Pharo from Squeak and what
>>> types of recent industrial projects youve come across that use Smalltalk? 
>>> 
>>> Also I wondered if you know of any active smalltalk group in Silicon Valley
>>> and what are the best forums for professional SmallTalk development.*
>>> 
>>> I would very much like to save their project as a Smalltalk project. The
>>> principal issue seems to be finding enough Smalltalk developers. I don't
>>> know if they need on-site developers or if remote developers can pass
>>> muster. I strongly suspect the former.
>>> 
>>> 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.
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>> 
>> 
> 
> 

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

[Sean P. DeNigris]

Denis Kudriashov wrote
> 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".

Wow, that sounds really cool. I'll have to play with it a bit to see how
much difference it makes in practice…



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

[Pharo-users] Pharo developers wanted in Toronto

[aglynn42]

Telna is looking for developers with Smalltalk experience, preferably Pharo,  
in Toronto Canada.

The role is listed on indeed.ca if anyone is interested.

Andrew Glynn

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

[Denis Kudriashov]

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".

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 :

> 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
>
>

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

[Herbert Vojčík]

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

Re: [Pharo-users] Pharo70 session start and silent failures

[Denis Kudriashov]

I had similar problem with SSDP server.
When I tried to stop it during shutdown of image the image didn't closed.
It hangs forever. In some cases I was able to open debugger which pointed
to exactly same place which you mentioned.
My guess was that process termination during shutdown is not safe anymore.
But I had no time to check deeply.



2018-05-03 16:13 GMT+03:00 Holger Freyther :

> I am facing a problem with the new SessionManager>>#snapshot:andQuit:
> code. I have had plenty Pharo70 images that didn't restore anymore as the
> code is waiting for the "wait" semaphore. For sure it is something my code
> is doing but could anyone think of ways to make it more robust and handle
> failures more gracefully? My main concerns are:
>
> * When the failure becomes noticeable it is too late. :(
> * It fails silently. Maybe WorkingSession>>#runStartup: shouldn't rely on
> the UIManager doing the right thing (before the UI was fully initialized?)
> * Debugging is hard, there is no indication of why it broke, and getting
> to the situation of breakage takes a bit of time (installing the
> baseline..).
>
> holger
>
>
>
>

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

[Ben Coman]

On 4 May 2018 at 08:02, Ramon Leon  wrote:

> On 05/03/2018 12:02 PM, Guillermo Polito wrote:
>
>> I don't think so... any compiler book talks about ASTs using acronyms.
>> Acronyms are good when acronyms are good.
>>
>
> Boo, acronyms bad, virtually always. Jargon is awful when speaking and
> awful when Smalltalk'ing, use words, they're not in short supply.
>
>
a TMA situation?