April 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to catch and handle multiple exceptions

by Sean P. DeNigris

Or I guess you don't even need dd here, just #handleMyErrorCase polymorphically ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 8, 2019

Re: [Pharo-users] How to catch and handle multiple exceptions

by Sean P. DeNigris

Tim Mackinnon wrote > nothing else springs to mind Double dispatch w extension methods on the Exception classes? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 8, 2019

Re: [Pharo-users] How to catch and handle multiple exceptions

by Stephan Eggermont

Tim Mackinnon <tim(a)testit.works> wrote: > > Thanks, I guess that makes sense, although it somehow looks a bit ugly > with the nested brackets.. but nothing else springs to mind so maybe Iâll > get used to it (and In my case I think itâs likely 2 or 3 different exceptions) I think I prefer them to be somehow ugly. I donât want to encourage you to nest and chain exceptions ð Stephan

April 7, 2019

Re: [Pharo-users] How to catch and handle multiple exceptions

by Tim Mackinnon

Thanks, I guess that makes sense, although it somehow looks a bit ugly with the nested brackets.. but nothing else springs to mind so maybe Iâll get used to it (and In my case I think itâs likely 2 or 3 different exceptions) Tim Sent from my iPhone > On 7 Apr 2019, at 20:43, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > > > This last one. > > [[self run] > on: TestFailure > do: [:testEx | ...]] > on: Error > do: [:error | ...]

April 7, 2019

Re: [Pharo-users] How to catch and handle multiple exceptions

by Richard Sargent

On Sun, Apr 7, 2019, 12:13 Tim Mackinnon <tim(a)testit.works> wrote: > Hi - Iâm wondering what the best way for handling multiple exceptions is > in Pharo? > > It seems like we just have on:do: (where on is a single exception?). > > However, I think Iâve noticed that you can concatenate exceptions - so > DomainError, ZnHttpUnsuccessful - and then pass that to on: > > However, Iâm not clear on how we then elegantly process the exception if > you want to do different things (which is often the case for unrelated > exceptions). I am kind of superseded there isnât on:do:on:do: (although > that seems quite ugly). > > So Iâm curious how you handle different exceptions without having some > sort of case statement in the exception handler? Or do you wrap exceptions > handlers over top of each other? > This last one. [[self run] on: TestFailure do: [:testEx | ...]] on: Error do: [:error | ...] > Tim >

April 7, 2019

How to catch and handle multiple exceptions

by Tim Mackinnon

Hi - Iâm wondering what the best way for handling multiple exceptions is in Pharo? It seems like we just have on:do: (where on is a single exception?). However, I think Iâve noticed that you can concatenate exceptions - so DomainError, ZnHttpUnsuccessful - and then pass that to on: However, Iâm not clear on how we then elegantly process the exception if you want to do different things (which is often the case for unrelated exceptions). I am kind of superseded there isnât on:do:on:do: (although that seems quite ugly). So Iâm curious how you handle different exceptions without having some sort of case statement in the exception handler? Or do you wrap exceptions handlers over top of each other? Tim

April 7, 2019

Re: [Pharo-users] Iceberg for files other than code?

by Tim Mackinnon

Hi Konrad - I think you can do what you describe - I think the ICeRepository entry for your project will have the path you want. And yes, its the committing back non source files where iceberg doesnât try to do anything (and so needs help from elsewhere). Tim > On 7 Apr 2019, at 16:40, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > > Hi Christopher and Tim, > > Thanks for your comments! > > I agree that managing the README from Pharo is not the most important > use case, I just mentioned it because everyone know what a README is. > > A better example of what I want to do is Pharo's Help system. It stores > the individual pages as methods that return a literal string. That's one > way to store data in a package but it looks like a kludge. More > importantly, it is very difficult to use or edit the pages outside of > Pharo. > > A better way to do something like that is to store pages as plain text > in the same repository as the classes that use them. But that requires > that the class can access the files as "file xx/yy/zz.txt in the same > repository from which my code was loaded". And if the class modifies the > text file, that change must be committed somehow. > > I suspect that the read access part is doable somehow. The repository > checkout in pharo-local contains all the files, so it's just a matter of > figuring out the path. It's committing changes that requires some > support from Iceberg, which you says is not available if I understand > correctly. > > Konrad >

April 7, 2019

Re: [Pharo-users] Iceberg for files other than code?

by Konrad Hinsen

Hi Christopher and Tim, Thanks for your comments! I agree that managing the README from Pharo is not the most important use case, I just mentioned it because everyone know what a README is. A better example of what I want to do is Pharo's Help system. It stores the individual pages as methods that return a literal string. That's one way to store data in a package but it looks like a kludge. More importantly, it is very difficult to use or edit the pages outside of Pharo. A better way to do something like that is to store pages as plain text in the same repository as the classes that use them. But that requires that the class can access the files as "file xx/yy/zz.txt in the same repository from which my code was loaded". And if the class modifies the text file, that change must be committed somehow. I suspect that the read access part is doable somehow. The repository checkout in pharo-local contains all the files, so it's just a matter of figuring out the path. It's committing changes that requires some support from Iceberg, which you says is not available if I understand correctly. Konrad

April 7, 2019

Re: [Pharo-users] difference between double dispatch and the method explains here

by Roelof Wobben

Op 6-4-2019 om 15:15 schreef K K Subbu: > On 06/04/19 4:49 PM, Roelof Wobben wrote: >> Hello, >> >> I just learned double dispatch. >> And now for the Robot challenge of exercism Tim has pointed me to >> this >> article(https://blog.metaobject.com/2019/04/accessors-have-message-obsessio… >> >> but I fail to see how the move method looks like in that article. >> I had a conversation with Tim in the exercism channel and the way he >> explains it, it looks like double dispatch for me. >> >> Am I on the right track or do I oversee something here. > unary methods like moveRight perform specific ops and are not > parametric, so only a single dispatch, depending on the receiver, is > needed. > > If you change it to move: aDistanceOrAngle, then performing requests > like "move: 3 cms" or "move: 30 degrees" will depend not only on the > receiver but also on the class of the argument. This would need double > dispatch (aka multiple polymorphism). The first dispatch would be > based on the receiver and the receiver's method would then dispatch it > based on the class of the argument (i.e. Distance>>move or Angle>>move ) > > HTH .. Subbu > > hmm, still stuck I have now a class Direction with as instance variables north, south, east, west and made the accessors. then I thought I need a initialize like this : initialize Â Â north = Direction( 0, -1). Â Â eastÂ = Direction( 1,Â 0). Â Â south = Direction( 0,Â 1). Â Â westÂ = Direction(-1,Â 0). but the Direction (0,-1)Â is a problem . the compiler does not like the (0,-1) part to give you the big picture. I have a Robot which can turnRight , turnLeft and moveForward and I try to understand how the page would work in my case. So I have a object Direction as described above and a Object MoveForward which is a subobject of Direction. MoveForward has only 1 method : IsMove Â Â ^Â 'A' Roelof

April 7, 2019

Re: [Pharo-users] Iceberg for files other than code?

by Tim Mackinnon

My understanding is that at the moment commits are restricted to whatâs I the designated src directory, so you need to use an external way to commit non code files into your branch. These can be 1. Git cmd line 2. Another tool like IntelliJ 3. The github web bowser If you do, you need to pull or merge in Pharo to keep things in sync. I also hope one day we might widen the scope to commit more things directly in Pharo - particularly the readme ir other config files (I gave the same problem with exercism ) Tim Sent from my iPhone > On 6 Apr 2019, at 22:45, Christopher Fuhrman <christopher.fuhrman(a)gmail.com> wrote: > > Hi Konrad, > >> On Sat, 6 Apr 2019 at 15:46, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: >> Hi everyone, >> >> Is it possible to read and modify files not containing Pharo code in a >> repository managed by Iceberg? I am thinking of reading the repository's >> README file, for example, or storing data files read by my code >> alongside the code itself. > > I'm not sure if you are referring to GitHub's README, but if you are, I maintain my project's README on GitHub's web site (which requires care if you're using branches). I like the markdown preview there which requires no fancy software installed on my PC. You need to pull the change to Iceberg. > > There's indeed a copy of the README.md in my image's pharo-local/iceberg/GITHUBUSERNAME/GITHUBPROJECT directory, and I can even modify it using Pharo 7's File Browser. However, any modifications to it are not seen or committed by Iceberg (at least I don't know of a way to make that happen). I believe Iceberg's change detection is limited to the smalltalk files in the packages that are in the repositories it knows about. But I'm still far from an expert with this. Hopefully a more qualified person can confirm. > > There's theoretically a way to run a git client outside of Pharo that knows about the local git repo that Iceberg's using, so maybe you can commit the non-Pharo files that way. However, doing that is sure to cause a "detached" state with the repo in the image. That is not a catastrophic problem, but it's more accidental complexity to deal with. I picked my battles and maintain README on GitHub. > > Christopher > >> >> Konrad. >> > > > -- > Christopher Fuhrman, P.Eng, PhD > Professor in the DÃ©partement of Software and IT Engineering > ÃTS (Ãcole de technologie supÃ©rieure) > > http://profs.etsmtl.ca/cfuhrman > +1 514 396 8638 > L'ÃTS est une constituante de l'UniversitÃ© du QuÃ©bec > Confidentiality Notice > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify christopher.fuhrman(a)etsmtl.ca. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. > Avis de confidentialitÃ© > L'information contenue dans ce message Ã©lectronique ainsi que dans les fichiers qui peuvent y Ãªtre attachÃ©s est de nature confidentielle et destinÃ©e Ã l'usage exclusif du destinataire. Si ce message vous est parvenu par erreur ou que vous n'Ãªtes pas le destinataire visÃ©, vous Ãªtes par la prÃ©sente avisÃ© que tout usage, copie ou distribution de l'information contenue dans ce message est strictement interdit et vous Ãªtes priÃ© d'en aviser christopher.fuhrman(a)etsmtl.ca et de dÃ©truire ce message.

April 6, 2019