Re: [Pharo-dev] Catching Exceptions without any notice

All forms of learning involve some degree criticism, and sometimes we learn the most from the hardest task masters. We all want a positive community, but we need to not fall into the trap of... "hacker forums where, out of some misguided sense of hyper-courtesy, participants are banned from postin

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 17:31, stepharo wrote: > > I did not expected such a warm welcome and being in vain for more than a >> year.. >> Thank you all guys, you are great! >> >> Yes, as i said i feel like i want to get some involvement.. So expect >> more acid in future, because that is my energy taki

Re: [Pharo-dev] Catching Exceptions without any notice

I did not expected such a warm welcome and being in vain for more than a year.. Thank you all guys, you are great! Yes, as i said i feel like i want to get some involvement.. So expect more acid in future, because that is my energy taking such unordinary form sometimes :) I'm really happy

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 14:13, Robert Withers wrote: > > > On 04/01/2016 05:40 PM, Aliaksei Syrel wrote: > >> >> Thanks for feedback :) >> >> Nevertheless, later I realized that blocks are evil, ... >> > > btw, why so? > One touch of a block of evil :) > > https://www.youtube.com/watch?v=Fw9IqUgGlzs

Re: [Pharo-dev] Catching Exceptions without any notice

On 04/01/2016 05:40 PM, Aliaksei Syrel wrote: Thanks for feedback :) Nevertheless, later I realized that blocks are evil, ... One touch of a block of evil :) https://www.youtube.com/watch?v=Fw9IqUgGlzs -- Robert . .. ...^,^

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 12:44, stepharo wrote: > Igor please use your energy helping us. > > I did not expected such a warm welcome and being in vain for more than a year.. Thank you all guys, you are great! Yes, as i said i feel like i want to get some involvement.. So expect more acid in future, be

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 12:45, stepharo wrote: > > Hi Igor, >> >> You are more than welcome to come back. >> >> Too much acidity is good neither for you nor for the people around you >> :). Let’s be kind with one another and assume that we all care and we want >> to make this world a better place, but

Re: [Pharo-dev] Catching Exceptions without any notice

"Used for centuries to preserve meat and fish, citric acid has innumerable health benefits. It increases the acidity of the bacterial environment, making it difficult for the microbes to survive and, more importantly, to reproduce." Applies to bugs and code smells. Phil On Sat, Apr 2, 2016 at 11

Re: [Pharo-dev] Catching Exceptions without any notice

Hi Igor, You are more than welcome to come back. Too much acidity is good neither for you nor for the people around you :). Let’s be kind with one another and assume that we all care and we want to make this world a better place, but that at the same time we are still only humans. +1 Espec

Re: [Pharo-dev] Catching Exceptions without any notice

Igor please use your energy helping us. Stef Le 1/4/16 22:47, Igor Stasenko a écrit : On 1 April 2016 at 21:52, stepharo > wrote: Hi I do not think that aliaksei is not taking care. He is working a lot to make sure that Pharo will have a future fro

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 03:06, Robert Withers wrote: > Good to see you again, Igor. Would it make sense to define instVar > initializers in the class object allowing the install of init forwarders in > the object slots on VM for a Squeak-style implicitly typed dependency > injection? Welcome. > > I wo

Re: [Pharo-dev] Catching Exceptions without any notice

Good to see you again, Igor. Would it make sense to define instVar initializers in the class object allowing the install of init forwarders in the object slots on VM for a Squeak-style implicitly typed dependency injection? Welcome. --- robert > On Apr 1, 2016, at 19:48, Igor Stasenko wrote: >

Re: [Pharo-dev] Catching Exceptions without any notice

Another approach would be to prefill the object with initial default values, so that it has no any inconsistency right from its birth. Even if your next statement has 99.9% chance to override these defaults, you eliminating this 0.01% that causing nil errors. That, of course, raising another proble

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 01:07, Tudor Girba wrote: > Hi Igor, > > You are more than welcome to come back. > > Thank you. > Too much acidity is good neither for you nor for the people around you :). > Let’s be kind with one another and assume that we all care and we want to > make this world a better

Re: [Pharo-dev] Catching Exceptions without any notice

On 2 April 2016 at 01:13, Henrik Nergaard wrote: > >Purpose of that catch, as mentioned by Nicolai, is indeed to ignore late > initialized objects. For example, imagine a Morph with height that is equal > to >owner's height. In this case one would write in #initialize: > > >Initialize > > > self

Re: [Pharo-dev] Catching Exceptions without any notice

>Purpose of that catch, as mentioned by Nicolai, is indeed to ignore late >initialized objects. For example, imagine a Morph with height that is equal to >>owner's height. In this case one would write in #initialize: >Initialize > self height: [ :morph | morph owner height ]. No. ownerChange

Re: [Pharo-dev] Catching Exceptions without any notice

Hi Igor, You are more than welcome to come back. Too much acidity is good neither for you nor for the people around you :). Let’s be kind with one another and assume that we all care and we want to make this world a better place, but that at the same time we are still only humans. Cheers, Doru

Re: [Pharo-dev] Catching Exceptions without any notice

Hi Aliaksei, Hi Stef, On Fri, Apr 1, 2016 at 2:40 PM, Aliaksei Syrel wrote: > Thanks for feedback :) > > Indeed, this is a nice case to learn from. That piece of code was written > when I just started working with pharo after coming from Java world. > > Purpose of that catch, as mentioned by Nic

Re: [Pharo-dev] Catching Exceptions without any notice

Thanks for feedback :) Indeed, this is a nice case to learn from. That piece of code was written when I just started working with pharo after coming from Java world. Purpose of that catch, as mentioned by Nicolai, is indeed to ignore late initialized objects. For example, imagine a Morph with hei

Re: [Pharo-dev] Catching Exceptions without any notice

On 1 April 2016 at 09:53, Tudor Girba wrote: > Hi, > > Nice to hear from you Igor. I am glad to see you around here. > > Hi, Doru. Yeah, i am considering whether i want to return to things i left, or not. So, expect more of my acid sarcasm in future. Maybe :) > I do not see how your quote appli

Re: [Pharo-dev] Catching Exceptions without any notice

On 1 April 2016 at 21:52, stepharo wrote: > Hi > > I do not think that aliaksei is not taking care. > He is working a lot to make sure that Pharo will have a future from the UI > perspective. He is spending all his free time > on Bloc and what he is doing is massive. He rewrote the AthensCairoBac

Re: [Pharo-dev] Catching Exceptions without any notice

Hi I do not think that aliaksei is not taking care. He is working a lot to make sure that Pharo will have a future from the UI perspective. He is spending all his free time on Bloc and what he is doing is massive. He rewrote the AthensCairoBack end to optimise it for Bloc local coordinates. I'm

Re: [Pharo-dev] Catching Exceptions without any notice

Hi, Nice to hear from you Igor. I am glad to see you around here. I do not see how your quote applies to the current case given that the original authors did not leave anywhere, but perhaps it was a joke, and I did not get it. Cheers, Doru > On Apr 1, 2016, at 5:54 AM, Igor Stasenko wrote: >

Re: [Pharo-dev] Catching Exceptions without any notice

A perfect example of careless programming. "I'll do it my way, and if it causing any problems, i don't care and i will just ignore them. And it's not my problem anyways, i went to something else already, since this part is works and DONE" :) On 30 March 2016 at 14:33, Nicolai Hess wrote: > Pleas

Re: [Pharo-dev] Catching Exceptions without any notice

Handling Error will be an improvement. But we don't know the rationale for handling Exception in the first place, if it's for ignoring some Warnings and Errors then changing the handler to Error would break things. I was trying to propose the less risky change, but I'm with you. The right solution

Re: [Pharo-dev] Catching Exceptions without any notice

> On Mar 31, 2016, at 3:51 AM, Gabriel Cotelli wrote: > > On the meantime at least change the handler to ignore the halts. > > ... on: Exception - Halt > > Should do the trick > Can someone say why ... on: Error will not improve things? Exception - Halt is just /wrong/, less wrong than E

Re: [Pharo-dev] Catching Exceptions without any notice

On the meantime at least change the handler to ignore the halts. ... on: Exception - Halt Should do the trick On Mar 31, 2016 06:57, "Esteban Lorenzano" wrote: > > On 30 Mar 2016, at 19:54, Aliaksei Syrel wrote: > > Do anyone really use GLM-Morphic-Brick? > > Because it is there just for spot

Re: [Pharo-dev] Catching Exceptions without any notice

> On 30 Mar 2016, at 19:54, Aliaksei Syrel wrote: > > Do anyone really use GLM-Morphic-Brick? > > Because it is there just for spotter and will be deleted ASAP. > > We know that it is bad. Normal fix requires too many changes... > but catching Exception is bad because it will catch all, even

Re: [Pharo-dev] Catching Exceptions without any notice

2016-03-31 10:51 GMT+02:00 Tudor Girba : > Hi Nicolai, > > Thank you for the feedback. Just, please let’s adopt a different tone. > > Cheers, > Doru > > > I am not sure what is wrong with my tone. I did not choose a random external library and starting to criticize it. This is a core component. A

Re: [Pharo-dev] Catching Exceptions without any notice

Hi Nicolai, Thank you for the feedback. Just, please let’s adopt a different tone. Cheers, Doru > On Mar 31, 2016, at 8:37 AM, Nicolai Hess wrote: > > > > 2016-03-30 19:54 GMT+02:00 Aliaksei Syrel : > Do anyone really use GLM-Morphic-Brick? > > We all "use" it, our tools are build with thi

Re: [Pharo-dev] Catching Exceptions without any notice

2016-03-30 19:54 GMT+02:00 Aliaksei Syrel : > Do anyone really use GLM-Morphic-Brick? > We all "use" it, our tools are build with this. (inspector/debugger/playground/spotter). > Because it is there just for spotter and will be deleted ASAP. > Not only for spotter. And if our tools are build wi

Re: [Pharo-dev] Catching Exceptions without any notice

Do anyone really use GLM-Morphic-Brick? Because it is there just for spotter and will be deleted ASAP. We know that it is bad. Normal fix requires too many changes... On Mar 30, 2016 1:34 PM, "Nicolai Hess" wrote: > Please don't do this: > > updateHeight > "no need to care about height, whe

Re: [Pharo-dev] Catching Exceptions without any notice

Nicolas Cellier wrote > Isn't catching too wide an anti-pattern? Yes! Just think of all the Exception subclasses which are *not* errors. This kind of thing effectively disables them. > 2016-03-30 13:33 GMT+02:00 Nicolai Hess < > nicolaihess@ > >: > >> Please don't do this: >> >> updateHeight

Re: [Pharo-dev] Catching Exceptions without any notice

Isn't catching too wide an anti-pattern? 2016-03-30 13:33 GMT+02:00 Nicolai Hess : > Please don't do this: > > updateHeight > "no need to care about height, when it's logic is not customized" > self layout isHeightCustom ifFalse: [ ^ self ]. > [ self bounds: (self brickBounds withHeig

[Pharo-dev] Catching Exceptions without any notice

Please don't do this: updateHeight "no need to care about height, when it's logic is not customized" self layout isHeightCustom ifFalse: [ ^ self ]. [ self bounds: (self brickBounds withHeight: self customHeight) ] on: Exception do: [ "just skip and do nothing" ] This