- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] about syntaxError

by Igor Stasenko

On 8 December 2016 at 22:56, stepharong <stepharong(a)free.fr> wrote: > Sorry igot but I do not understand what you are saying. > Too tired. > the exception handler if it runs in UI process does following: - spawns new UI process, suspending the old one, that caused exception, then creates a debugger that showing where the original exception occur. but if you put halt somewhere in the middle of exception handler , you will either create an endless loop (of attempting to bring debugger), or, when you lucky, as in your case - it will show you debugger , where you interrupted the exception handling, but not the original exception. > > coz u putting exception inside an exception handler.. > yo gawd, so you like exceptions? > lets put an exception inside your exception, so it will be thrown while it > thrown > :)))))) > (i hope everyone knows this reference :) > > > On 8 December 2016 at 22:07, stepharong <stepharong(a)free.fr> wrote: > >> I tried to fix the extract method refactoring that seems broken when >> extracting class or variables. >> And I wanted to understand if I can get a debugger stack instead of this >> useless Syntax Error: window. >> Now I cannot find reference to SyntaxErrorDebugger. >> still putting a break point in >> >> buildMorphicViewOn: aSyntaxError >> "Answer an Morphic view on the given SyntaxError." >> >> | window | >> self halt. >> >> bring a debugger but with a cut stack .... >> >> open: aSyntaxError >> "Answer a standard system view whose model is an instance of me." >> <primitive: 19> >> "Simulation guard" >> | process | >> process := Processor activeProcess. >> UIManager default spawnNewProcessIfThisIsUI: process. >> UIManager default defer: [ >> self buildMorphicViewOn: aSyntaxError. >> ]. >> ^ process suspend >> >> so it does not really help to understand the syntax error. >> I do not get why this is so opaque. >> >> Stef >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ >> >> > > > -- > Best regards, > Igor Stasenko. > > > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > -- Best regards, Igor Stasenko.

Dec. 9, 2016

Re: [Pharo-dev] about syntaxError

by Henrik Nergaard

Change line 3 of RBExtractMethodRefactoring>>extractMethod to something like: [ extractedParseTree := RBParser parseExpression: extractCode ] on: SyntaxErrorNotification do: [ :ex| ex debug ]. To bring up a debugger. Best regards, Henrik -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of stepharong Sent: Thursday, December 8, 2016 9:08 PM To: pharo-dev(a)lists.pharo.org Subject: [Pharo-dev] about syntaxError I tried to fix the extract method refactoring that seems broken when extracting class or variables. And I wanted to understand if I can get a debugger stack instead of this useless Syntax Error: window. Now I cannot find reference to SyntaxErrorDebugger. still putting a break point in buildMorphicViewOn: aSyntaxError "Answer an Morphic view on the given SyntaxError." | window | self halt. bring a debugger but with a cut stack .... open: aSyntaxError "Answer a standard system view whose model is an instance of me." <primitive: 19> "Simulation guard" | process | process := Processor activeProcess. UIManager default spawnNewProcessIfThisIsUI: process. UIManager default defer: [ self buildMorphicViewOn: aSyntaxError. ]. ^ process suspend so it does not really help to understand the syntax error. I do not get why this is so opaque. Stef -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016

Re: [Pharo-dev] Archive for Monthly Pharo Newsletter

by stepharong

This is cool like that I link to it from the pharoweekly blg > Hi, > > There is an archive for the monthly newsletter: > > http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486… > > I will add that link to the website. > > Marcus -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016

Re: [Pharo-dev] about syntaxError

by stepharong

Sorry igot but I do not understand what you are saying. Too tired. > coz u putting exception inside an exception handler.. > yo gawd, so you like exceptions? > lets put an exception inside your exception, so it will be thrown while > it thrown:)))))) > (i hope everyone knows this reference :) > > > On 8 December 2016 at 22:07, stepharong <stepharong(a)free.fr> wrote: >> I tried to fix the extract method refactoring that seems broken when >> extracting class or variables. >> And I wanted to understand if I can get a debugger stack instead of >> this useless Syntax Error: window. >> Now I cannot find reference to SyntaxErrorDebugger. >> still putting a break point in >> >> buildMorphicViewOn: aSyntaxError >> "Answer an Morphic view on the given SyntaxError." >> >> | window | >> self halt. >> >> bring a debugger but with a cut stack .... >> >> open: aSyntaxError >> "Answer a standard system view whose model is an instance of me." >> <primitive: 19> >> "Simulation guard" >> | process | >> process := Processor activeProcess. >> UIManager default spawnNewProcessIfThisIsUI: process. >> UIManager default defer: [ >> self buildMorphicViewOn: aSyntaxError. >> ]. >> ^ process suspend >> >> so it does not really help to understand the syntax error. >> I do not get why this is so opaque. >> >> Stef >> >> >> --Using Opera's mail client: http://www.opera.com/mail/ >> > > > > --Best regards, > Igor Stasenko. -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016

Re: [Pharo-dev] [ANN] Pharo Association has a new Website!

by Sven Van Caekenberghe

> On 8 Dec 2016, at 19:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> >>> Accepting Bitcoin payments would be a plus ;-) (https://bitpay.com/tour) >>> >> > > Hi, > > I have setup bitpay. This means we can now accept bitcoin, to pay by bitcoin, > for now please select âofflineâ payment and then send a mail to > association(a)pharo.org > > and we will generate a bitcoin invoice. (we can integrate it a bit better later). > > Marcus Nice!

Dec. 8, 2016

Re: [Pharo-dev] about syntaxError

by Igor Stasenko

coz u putting exception inside an exception handler.. yo gawd, so you like exceptions? lets put an exception inside your exception, so it will be thrown while it thrown :)))))) (i hope everyone knows this reference :) On 8 December 2016 at 22:07, stepharong <stepharong(a)free.fr> wrote: > I tried to fix the extract method refactoring that seems broken when > extracting class or variables. > And I wanted to understand if I can get a debugger stack instead of this > useless Syntax Error: window. > Now I cannot find reference to SyntaxErrorDebugger. > still putting a break point in > > buildMorphicViewOn: aSyntaxError > "Answer an Morphic view on the given SyntaxError." > > | window | > self halt. > > bring a debugger but with a cut stack .... > > open: aSyntaxError > "Answer a standard system view whose model is an instance of me." > <primitive: 19> > "Simulation guard" > | process | > process := Processor activeProcess. > UIManager default spawnNewProcessIfThisIsUI: process. > UIManager default defer: [ > self buildMorphicViewOn: aSyntaxError. > ]. > ^ process suspend > > so it does not really help to understand the syntax error. > I do not get why this is so opaque. > > Stef > > > -- > Using Opera's mail client: http://www.opera.com/mail/ > > -- Best regards, Igor Stasenko.

Dec. 8, 2016

Re: [Pharo-dev] Archive for Monthly Pharo Newsletter

by Sven Van Caekenberghe

Wow, this is very nice! > On 8 Dec 2016, at 17:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > There is an archive for the monthly newsletter: > > http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=0486… > > I will add that link to the website. > > Marcus

Dec. 8, 2016

about syntaxError

by stepharong

I tried to fix the extract method refactoring that seems broken when extracting class or variables. And I wanted to understand if I can get a debugger stack instead of this useless Syntax Error: window. Now I cannot find reference to SyntaxErrorDebugger. still putting a break point in buildMorphicViewOn: aSyntaxError "Answer an Morphic view on the given SyntaxError." | window | self halt. bring a debugger but with a cut stack .... open: aSyntaxError "Answer a standard system view whose model is an instance of me." <primitive: 19> "Simulation guard" | process | process := Processor activeProcess. UIManager default spawnNewProcessIfThisIsUI: process. UIManager default defer: [ self buildMorphicViewOn: aSyntaxError. ]. ^ process suspend so it does not really help to understand the syntax error. I do not get why this is so opaque. Stef -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016

Re: [Pharo-dev] :: Separator in class names

by stepharong

We are working on a module system. When it will be ready we will mention it. Stef On Thu, 08 Dec 2016 02:39:36 +0100, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > Torsten, > > Because of the obvious portability problems this would introduce, I > would think that an attempt should be made to come up with a common > namespace solution ... > > I do believe that some discussion about namespace alternatives has taken > place between GemStone and Pharo --- not familiar with details or > outcome of discussions, but I would like to think that at least an > attempt was made to come up with a common solution before resorting to a > unilateral solution that would only introduce more isolation between the > various dialects --- something that a small community cannot really > afford to do ... > > Dale > > On 12/07/2016 04:47 PM, Torsten Bergmann wrote: >> Hi, >> >> due to the absence of a namespace solution we today often prefix >> classes with one, two or three letters. >> You all know prefixes like "Zn", "Zdc", "GLM", "Tx", "WA", ... to avoid >> conflicting names. >> >> I would like to have a "::" separator within the class name to better >> distinguish >> the class name from the prefix and increase readability at the same >> time. SmalltalkMT >> had this solution in alignment with C++ and I really liked working with >> it. >> So much that I would like to see it in Pharo too - maybe also as a base >> for future Namespace >> additions. >> >> So I modified the #isValidGlobalName in Pharo 6.0 like mentioned below >> to allow and support >> the :: notation for classes. After that I can create classes like: >> >> Seaside::Component >> Core::Boolean >> Model::Person >> GLM::BrickListModel >> Tx::FontAttribute >> >> so far without any problem. >> >> Do you think >> - there will be places where this conflicts or creates hazzles >> (tools, metacello, ...) >> - if it would be a good idea to add this to the default image? >> >> Thanks for feedback. >> >> Thx >> T. >> >> -------------------------------------------------------------------------------------------------- >> isValidGlobalName >> >> self ifEmpty: [ ^ false ]. >> >> "reserverd default names" >> self = 'NameOfSubclass' ifTrue: [ ^ false ]. >> self = 'TNameOfTrait' ifTrue: [ ^ false ]. >> >> (self occurrencesOf: $:) = 2 ifTrue: [ >> ^(self splitOn: '::') allSatisfy: [: part | part isValidGlobalName ] >> ]. >> >> ^ Character supportsNonASCII >> ifTrue: [ >> (self first isLetter >> and: [self first isUppercase]) >> and: [ self allSatisfy: [:character | >> character isAlphaNumeric or: [ character = $_ ]]]] >> ifFalse: [ >> (self first between: $A and: $Z) and: [ >> self allSatisfy: [:character | >> (character between: $a and: $z) or: [ >> (character between: $A and: $Z) or: [ >> (character between: $0 and: $9) or: [ >> character = $_]]]]]] >> > > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016

Re: [Pharo-dev] Drastically improving the messageNotUnderstood title

by stepharong

On Thu, 08 Dec 2016 07:35:59 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> 2016-12-07 21:44 GMT+01:00 stepharong <stepharong(a)free.fr>: >>>> >>>> Hi guys >>>> >>>> As I exposed newbies to our wonderfull debugger I think that we should >>>> change >>>> >>>> MessageNotUnderstood: Class>>#message >>>> >>>> into >>>> >>>> an instance of Class did not understand message >> >> Perhaps(?) a short form can be put in brackets? >> ==> an instance of Class did not understand #message sent to it (MNU >> Class>>#message) > > +1 good idea! > >> cheers -ben >> >>>> >>>> To me this simple change would have a HUGE impact on making the >>>> debugger >>>> first contact a lot more friendly. > > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 8, 2016