[Pharo-dev] [pharo-project/pharo-core] 76df96: 40302

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 76df96847be893c7edd4a03da2500c37f7a68530 https://github.com/pharo-project/pharo-core/commit/76df96847be893c7edd4a03da2500c37f7a68530 Author: Jenkins Build Server Date: 2014-10-14 (Tue, 14 Oct 2014

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

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

Re: [Pharo-dev] Mysteries of the compiler

> On 12 Oct 2014, at 11:49, Nicolai Hess wrote: > > I tried to solve issues > "13260 inspecting variables in the debugger fails in some cases" and > "14058 Inconsistent information in debugger" > and found some oddities in the way opal (compiler and the debuggermap) > handles tempory variables.

Re: [Pharo-dev] OSProcess in 3.0

On Tue, Oct 14, 2014 at 07:19:10AM +0200, Thierry Goubier wrote: > Hi Dave, > > took me a while to do some testing. It seems there is an issue, but I > couldn't find out where. First, the data: > > Loading a package from a local gitfiletree repository (get from the > command a zipped git archiv

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

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

[Pharo-dev] [pharo-project/pharo-core] e6023c: 40303

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e6023ca6f707a9c2b2dead79a9af5e4629171a3c https://github.com/pharo-project/pharo-core/commit/e6023ca6f707a9c2b2dead79a9af5e4629171a3c Author: Jenkins Build Server Date: 2014-10-14 (Tue, 14 Oct 2014

Re: [Pharo-dev] BlockClosure source code

> On 10 Oct 2014, at 12:29, Marcus Denker wrote: > > >> On 10 Oct 2014, at 10:57, Jan Kurš > > wrote: >> >> Hi All, >> >> Thank you for the replies. I see it is not an easy bug to fix. Do you have >> any idea, when this can be fixed? >> > I will try to fix it next

Re: [Pharo-dev] BlockClosure source code

Very nice !! On 14 Oct 2014, at 16:42, Marcus Denker wrote: >> >> On 10 Oct 2014, at 12:29, Marcus Denker wrote: >> >> >>> On 10 Oct 2014, at 10:57, Jan Kurš wrote: >>> >>> Hi All, >>> >>> Thank you for the replies. I see it is not an easy bug to fix. Do you have >>> any idea, when this

[Pharo-dev] [pharo-project/pharo-core] 3512dd: 40304

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3512dd8cc3b01799689e6fbe98c980fcb66e94f8 https://github.com/pharo-project/pharo-core/commit/3512dd8cc3b01799689e6fbe98c980fcb66e94f8 Author: Jenkins Build Server Date: 2014-10-14 (Tue, 14 Oct 2014

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

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

Re: [Pharo-dev] Mysteries of the compiler

Hi Marcus, On Tue, Oct 14, 2014 at 4:09 AM, Marcus Denker wrote: > > > On 12 Oct 2014, at 11:49, Nicolai Hess wrote: > > > > I tried to solve issues > > "13260 inspecting variables in the debugger fails in some cases" and > > "14058 Inconsistent information in debugger" > > and found some oddit

[Pharo-dev] Trouble opening large files

Hi, just debug it. I guess some primitive returns false instead of the basic filesize. There is AbstractFileReference>>humanReadableSize looking like this: humanReadableSize ^self size humanReadableSIByteSize So if size returns "false" then you will get this error. If you trace further you

Re: [Pharo-dev] Mysteries of the compiler

Thank you eliot, marcus Yes I know your blog it is a great source of information. I am curious how the squeak compiler/debugger handles this (I'll look into it). About opal and optimized block scope: Yes, I like the way this "special" non-scope is modelled with its own scope class. But somehow th

Re: [Pharo-dev] Mysteries of the compiler

On Tue, Oct 14, 2014 at 11:15 AM, Nicolai Hess wrote: > Thank you eliot, marcus > > Yes I know your blog it is a great source of information. > I am curious how the squeak compiler/debugger handles this (I'll look into > it). > There's no scope at run-time, only at compile time. AT compile time

Re: [Pharo-dev] OSProcess in 3.0

Le 14/10/2014 14:15, David T. Lewis a écrit : On Tue, Oct 14, 2014 at 07:19:10AM +0200, Thierry Goubier wrote: Hi Dave, took me a while to do some testing. It seems there is an issue, but I couldn't find out where. First, the data: Loading a package from a local gitfiletree repository (get f

Re: [Pharo-dev] Mysteries of the compiler

2014-10-14 20:31 GMT+02:00 Eliot Miranda : > > > On Tue, Oct 14, 2014 at 11:15 AM, Nicolai Hess wrote: > >> Thank you eliot, marcus >> >> Yes I know your blog it is a great source of information. >> I am curious how the squeak compiler/debugger handles this (I'll look >> into it). >> > > There's

Re: [Pharo-dev] BlockClosure source code

I love these little things. This is a great example of how value should not be confused with cost. Small can be quite big after all :) Doru On Tue, Oct 14, 2014 at 4:46 PM, Sven Van Caekenberghe wrote: > Very nice !! > > On 14 Oct 2014, at 16:42, Marcus Denker wrote: > > >> > >> On 10 Oct 201

[Pharo-dev] creating custom browsers out of GTInspector extensions

Hi, Now, that more people are playing with the GTInspector, I would like to raise another point that might otherwise go unnoticed: The inspector extensions do not only work in the inspector, but can also be combined in other browsers as well. For example, the attached picture shows a Pillar brows

Re: [Pharo-dev] Tests around Pharo

Well thank you again for your advices. We'll do operations for slices around 11-12 o'clock. For tests that Hilaire proposed (Dr Geo), we met some pharo committers during events in our university, and they suggested us to work mainly around collections, so we decided to focus to Collections part du

Re: [Pharo-dev] BlockClosure source code

> On 14 Oct 2014, at 22:01, Tudor Girba wrote: > > I love these little things. > > This is a great example of how value should not be confused with cost. Small > can be quite big after all :) It should be noted that there is almost no code “wasted” on this… the parser that creates the object

Re: [Pharo-dev] creating custom browsers out of GTInspector extensions

> On 14 Oct 2014, at 23:26, Tudor Girba wrote: > > Hi, > > Now, that more people are playing with the GTInspector, I would like to raise > another point that might otherwise go unnoticed: The inspector extensions do > not only work in the inspector, but can also be combined in other browsers

Re: [Pharo-dev] [squeak-dev] Re: [Pharo-users] Trouble opening large files

Do we create an issue for the Pharo-vm? Stef On 14/10/14 21:29, Nicolai Hess wrote: Ah, good to know. At least for squeak, bug 7522 can be closed :) Nicolai 2014-10-14 20:49 GMT+02:00 Eliot Miranda >: Hi Nicolai, On Tue, Oct 14, 2014 at 11:26 AM, Nic