Re: [Pharo-dev] Unwind error during termination

Ok I have the error too. Strangely enough, the error is triggered because the third BlockClosure>>#on:do: context has 2 temporaries instead of 3. Igor / Esteban do you have a clue ? Why a context would have less temporaries than expected ? Problem from context creation out of the stack ? I will

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

While I agree that we shouldn’t unnecessary make life more difficult for external frameworks/libraries when that can be avoided, we do have to reserve the right to be able to make changes that break things. Like with #includesSubstring: the actual intention of the change is valid and sound, but

Re: [Pharo-dev] VM for Athens Graphics

On 24 October 2013 08:24, Norbert Hartl wrote: > > > Am 23.10.2013 um 23:28 schrieb Igor Stasenko : > > > > > On 23 October 2013 23:13, Stéphane Ducasse wrote: > >> >>> >> Well implementing ARM-FFI is largely orthogonal to Athens. >> Yes, i am happily using it for Cairo and it lets me customize /

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

From the comments I think we can agree that it is a better to have a lint rule instead of breaking things the way it was introduced by the original issue #11876.    I therefore opened an issue    https://pharo.fogbugz.com/f/cases/11989/shouldnt-raise-Error-from-issue-11876-is-too-offensive and

Re: [Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

On 24 Oct 2013, at 13:55, Torsten Bergmann wrote: > From the comments I think we can agree that it is a better to have a lint rule > instead of breaking things the way it was introduced by the original issue > #11876. > > I therefore opened an issue > > https://pharo.fogbugz.com/f/cases/

Re: [Pharo-dev] Startup Preferences: An Alternative

you mean: CodeImporter evaluateString: (ZnEasy get: 'my-url') contents. :) On Oct 23, 2013, at 11:17 PM, Igor Stasenko wrote: > > On 23 October 2013 20:21, Sven Van Caekenberghe wrote: > This is really cool, is that in the image already ? > What about plain HTTP repos ? > > > indeed, what

Re: [Pharo-dev] Startup Preferences: An Alternative

And to save on parenthesis, you could also write Compiler evaluate: 'http://my.url.with.script.st' asZnUrl retrieveContents. CodeImporter evaluateString: 'http://my.url.with.script.st' asUrl retrieveContents. With #asUrl and #asZnUrl soon to be 100% the same thing. On 24 Oct 2013, at 14:32,

Re: [Pharo-dev] Startup Preferences: An Alternative

On 24 October 2013 14:42, Sven Van Caekenberghe wrote: > And to save on parenthesis, you could also write > > Compiler evaluate: 'http://my.url.with.script.st' asZnUrl > retrieveContents. > > CodeImporter evaluateString: 'http://my.url.with.script.st' asUrl > retrieveContents. > > this is why i

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On 24 October 2013 08:17, Philippe Marschall < philippe.marsch...@netcetera.ch> wrote: > On 22.10.13 00:08, Camillo Bruni wrote: > >> see my long explanation here https://pharo.fogbugz.com/** >> default.asp?11876#87218 >> it looks unsuspicous unti

[Pharo-dev] [pharo-project/pharo-core] 9e1723: 30520

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 9e1723ff19630cd7c4ffda1634be0f3200e2ba64 https://github.com/pharo-project/pharo-core/commit/9e1723ff19630cd7c4ffda1634be0f3200e2ba64 Author: Jenkins Build Server Date: 2013-10-24 (Thu, 24 Oct 2013

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30520 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On 24.10.13 15:24, Igor Stasenko wrote: On 24 October 2013 08:17, Philippe Marschall mailto:philippe.marsch...@netcetera.ch>> wrote: On 22.10.13 00:08, Camillo Bruni wrote: see my long explanation here https://pharo.fogbugz.com/__default.asp?11876#87218

Re: [Pharo-dev] Release mails and update summary

On Wed, Oct 23, 2013 at 10:54 AM, Torsten Bergmann wrote: > "Pharo launcher" [1] has the ability to download and run images. It really > helps avoiding chaos on the hard disk and I can only recommend to others > to give it a try. I agree! -- Damien Cassou http://damiencassou.seasidehosting.st

[Pharo-dev] Smalltalkhub commit dates broken?

Commit dates seem to be wrong. I committed a few packages in Moose/PetitDelphi today, and find them back as 17/05/2013 Stephan

Re: [Pharo-dev] Unwind error during termination

Clément Bera wrote: Ok I have the error too. Strangely enough, the error is triggered because the third BlockClosure>>#on:do: context has 2 temporaries instead of 3. Igor / Esteban do you have a clue ? Why a context would have less temporaries than expected ? Problem from context creation

Re: [Pharo-dev] Unwind error during termination

Le 24/10/2013 16:28, b...@openinworld.com a écrit : Clément Bera wrote: Ok I have the error too. Strangely enough, the error is triggered because the third BlockClosure>>#on:do: context has 2 temporaries instead of 3. Igor / Esteban do you have a clue ? Why a context would have less temporar

Re: [Pharo-dev] Startup Preferences: An Alternative

Ah ah yeah sure is cool. Now I was explaining some Seaside stuff to a friend who is doing .Net and he had a hard time grasping the thing. Phil , October 24, 2013, Igor Stasenko wrote: > > > > On 24 October 2013 14:42, Sven Van Caekenberghe wrote: >> >> And to save on parenthesis, you could al

Re: [Pharo-dev] Smalltalkhub commit dates broken?

The creation of the MC packages are from today too? Cheers, Nico Stephan Eggermont writes: > Commit dates seem to be wrong. I committed a few packages in > Moose/PetitDelphi today, > and find them back as 17/05/2013 > > Stephan -- Nicolas Petton http://nicolas-petton.fr

Re: [Pharo-dev] Smalltalkhub commit dates broken?

Nico wrote: >The creation of the MC packages are from today too? Name: PetitDelphi-StephanEggermont.129 Author: StephanEggermont Time: 24 October 2013, 3:54:21.159 pm UUID: b310f98a-41cf-4dd6-8be4-d1954ae69e4b Ancestors: PetitDelphi-StephanEggermont.128 Moved some AST classes

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On 24 October 2013 15:40, Philippe Marschall < philippe.marsch...@netcetera.ch> wrote: > On 24.10.13 15:24, Igor Stasenko wrote: > >> >> >> >> On 24 October 2013 08:17, Philippe Marschall >> >> > >> wrote: >> >> On 22.10.13 00:08, Camillo Bruni wrote:

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On Thu, 24 Oct 2013, Philippe Marschall wrote: On 22.10.13 00:08, Camillo Bruni wrote: see my long explanation here https://pharo.fogbugz.com/default.asp?11876#87218 it looks unsuspicous until the moment you try understand such a failing assertion. This isn't moving Pharo foward. This doesn'

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On 24 Oct 2013, at 18:32, Levente Uzonyi wrote: > On Thu, 24 Oct 2013, Philippe Marschall wrote: > >> On 22.10.13 00:08, Camillo Bruni wrote: >>> see my long explanation here >>> https://pharo.fogbugz.com/default.asp?11876#87218 >>> it looks unsuspicous until the moment you try understand such

Re: [Pharo-dev] Use #shouldnt:raise: only with specific errors, or evaluate the given expression directly

On 24 Oct 2013, at 18:32, Levente Uzonyi wrote: > On Thu, 24 Oct 2013, Philippe Marschall wrote: > >> On 22.10.13 00:08, Camillo Bruni wrote: >>> see my long explanation here >>> https://pharo.fogbugz.com/default.asp?11876#87218 >>> it looks unsuspicous until the moment you try understand such

Re: [Pharo-dev] Unwind error during termination

On Thu, Oct 24, 2013 at 12:10 AM, Clément Bera wrote: > Ok I have the error too. > > Strangely enough, the error is triggered because the third > BlockClosure>>#on:do: context has 2 temporaries instead of 3. > > Igor / Esteban do you have a clue ? Why a context would have less > temporaries than e

Re: [Pharo-dev] Unwind error during termination

OK I'll wait for another use case or until it happened to me. Like a usecase from a fresh image. It's just it may be due to the new inspector, new debugger or new compiler. Just wondering. 2013/10/24 Eliot Miranda > > > > On Thu, Oct 24, 2013 at 12:10 AM, Clément Bera wrote: > >> Ok I have the

[Pharo-dev] ensureCreateDirectory?

Out of curiosity, what was the motivation behind Issue 10924: Simplifying ensure* and create protocol? For me #ensureCreateDirectory is less intention revealing than #ensureDirectory because the "ensure" means "create only if necessary", not "definitely create" a directory. What am I missing? Than

Re: [Pharo-dev] Unwind error during termination

On Thu, Oct 24, 2013 at 11:25 AM, Clément Bera wrote: > OK I'll wait for another use case or until it happened to me. Like a > usecase from a fresh image. > > It's just it may be due to the new inspector, new debugger or new > compiler. Just wondering. > It's definitely not due to the new code.

[Pharo-dev] UpdatingMenuMorph

What happened to it and why? I'm porting TWM to 3.0 and didn't find any mention of removal on the dev or issue mailing list... Thanks. - Cheers, Sean -- View this message in context: http://forum.world.st/UpdatingMenuMorph-tp4716928.html Sent from the Pharo Smalltalk Developers mailing list

Re: [Pharo-dev] Unwind error during termination

I doubt that the reason is some bug in VM, i suspecting much simpler explanation: if you look at the bottom of stack, it starts from on:fork: it tries to deliver announcement.. and everything goes well until it gets an exception: PharoLauncher class(Object)>>doesNotUnderstand: #quitOnLaunch the

Re: [Pharo-dev] Unwind error during termination

the stack looks quite strange.. but if you open the debugger on that unwind error and see the #resume: context, evaluating: self isDead yields to true. it is a mystery however, how #resume: end up on the stack, when you just closing the debugger window and terminating the process. it seems like th

Re: [Pharo-dev] Unwind error during termination

ok, it seems i found how to reproduce the situation with following: [ [ 1/0 ] ensure: [ nil foo ] ] on: Error fork: [ :ex | 1halt ] you will get halt, and if you close the debugger , it will throw unwind error. (while instead it should throw DNU) -- Best regards, Igor Stasenko.

Re: [Pharo-dev] UpdatingMenuMorph

On 24 oct. 2013, at 22:07, Sean P. DeNigris wrote: > What happened to it and why? I'm porting TWM to 3.0 and didn't find any > mention of removal on the dev or issue mailing list... Thanks. It was removed in 30507. The decision to remove it has been made during the august sprint. I just remembe

Re: [Pharo-dev] Unwind error during termination

Hard to debug this kind of code :( This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, this is another flaw in exception handling, along with wrong handler for nested exception (testHandlerFromAction below), unless it's an avatar. Still, I do not see how you get the errorSubs

[Pharo-dev] API docs?

Hi all, I'm wondering if there are online API docs like there are for Java (here's a link for all you non-Java types). I've already got a copy of 'Pharo by Example' and 'A Guide to Work with Squeak Morph Classes', but neither are what I'm looking for.

Re: [Pharo-dev] Unwind error during termination

On 25 October 2013 00:26, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > Hard to debug this kind of code :( > This is reproducible on Squeak wiht on:do:, so on:fork: bizareness apart, > this is another flaw in exception handling, along with wrong handler for > nested exception (tes

Re: [Pharo-dev] Unwind error during termination

The author of the test is Andreas Raab, but I'm not sure who found it (excavating mailing list is hard work) 2013/10/25 Igor Stasenko > > > > On 25 October 2013 00:26, Nicolas Cellier < > nicolas.cellier.aka.n...@gmail.com> wrote: > >> Hard to debug this kind of code :( >> This is reproducible

Re: [Pharo-dev] Unwind error during termination

On 25 October 2013 01:28, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > The author of the test is Andreas Raab, but I'm not sure who found it > (excavating mailing list is hard work) > > and this test is missing in pharo, so thanks anyways :) i can't imagine what can't go wrong i

Re: [Pharo-dev] API docs?

projectVALIS wrote: > I'm wondering if there are online API docs like there are for Java (here's a > link for all you non-Java > types). I've already got a copy of 'Pharo by Example' and 'A Guide to Work > with Squeak Morph Classes', but neither are wha

Re: [Pharo-dev] API docs?

perfect! this is enough to get me going -- thanks!!! -- View this message in context: http://forum.world.st/API-docs-tp4716945p4717010.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.