I originally thought something was wrong when I could not browse the
code of a SLICE using Monticello. After hunting around I found [1]
saying this is expected behaviour. However I then suggest the following
enhancement:
Have the right-pane of the Monticello Repositoy Inspector be a tree
vi
106 classes done
537 classes remaining
Continuing in Compiler...
Today: CommentNode
Comment Of The Day Contest - One Day One Comment
Rules:
#1: Each day a not commented class is elected. Each day the best comment will
be integrated with name of the author(s).
#2: If you cannot comment it,
Yes, so duplicating the Compiler can't be a valid strategy. Every
Inspector, every Debugger, every message send will modify the binary
image...
You could trace the image with another program - or another trusted
image ;) - and validate some restrictive invariants, for example like:
- all behaviours
On 8 February 2012 12:33, Norbert Hartl wrote:
>
> Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
>
>> On 02/08/2012 10:43 AM, Marcus Denker wrote:
>>>
>>> On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
>>>
> well I do not think so since we can all read the code.
No, read
Stef,
I tried to push this to the inbox, but there was a problem, and "the
administrator has been notified." Oh well.
Attachments work. Attached are my FFI extensions, including non-aligned (with
which I have been able to slide so far???) double arrays, catalog (schema)
information for ODBC,
That one is not quite as easy:)
Dale
- Original Message -
| From: "Camillo Bruni"
| To: Pharo-project@lists.gforge.inria.fr
| Sent: Wednesday, February 8, 2012 4:03:40 AM
| Subject: Re: [Pharo-project] Migrating to Gemstone
|
| Well the main thing here is that I still have to manually c
On Wed, Feb 8, 2012 at 6:08 PM, Mariano Martinez Peck wrote:
>
>
> On Wed, Feb 8, 2012 at 4:04 PM, Nicolas Cellier <
> nicolas.cellier.aka.n...@gmail.com> wrote:
>
>> I think that my first proposition was more a negative speculation than
>> a really useful comment.
>> It was more to emphasize the
On Wed, Feb 8, 2012 at 4:04 PM, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
> I think that my first proposition was more a negative speculation than
> a really useful comment.
> It was more to emphasize the hackish nature of this change than to
> help future readers ;)
>
>
Even if
14322
-
Issue 5170: DNU Inspector>>arrowKey:from:
http://code.google.com/p/pharo/issues/detail?id=5170
Issue 5252: Cannot right click
http://code.google.com/p/pharo/issues/detail?id=5252
Issue 4650: Strange $ evaluates to Character arrowUp
http://code.google
You are right. The compiler binary described in the scenario
corresponds to the whole of the Smalltalk binary image.
Nicolas Cellier wrote:
Do you really think that the compiler is the real Achille heal in an
image where everything work by message send?
IMO, the compiler is much less central t
Do you really think that the compiler is the real Achille heal in an
image where everything work by message send?
IMO, the compiler is much less central than in other languages.
What I would do to fool users and tools would just be to hack a few
methods like #methodDict (just like Stephane propose
look into the gofer chapter on pbe2
Stef
On Feb 7, 2012, at 8:29 PM, Benjamin wrote:
> Would it be possible to write some kind of import / migrate script for
> ss3.gemstone.com?
>
> The following lines copy the complete version history to an *existing*
> project on gemstone:
>
> Gofer
I passed the info to nicolas and he will probably reply.
stef
On Feb 8, 2012, at 1:11 AM, Igor Stasenko wrote:
> On 7 February 2012 21:35, Sven Van Caekenberghe wrote:
>>
>> On 07 Feb 2012, at 16:58, Frank Shearar wrote:
>>
>>> Looks like it's dead. The machine's alive, and the HTTP server's
I think that my first proposition was more a negative speculation than
a really useful comment.
It was more to emphasize the hackish nature of this change than to
help future readers ;)
If you really want to include this change, I think you shall mention
the true purpose of this hack, and I guess
mariano can you add a bug entry and we integrate it.
Stef
On Feb 7, 2012, at 1:00 AM, Nicolas Cellier wrote:
> How many senders of #methodDict would miss-behave?
> No risk to throw away a freshly basicAddedSelector:withMethod: ?
> Or should the IDE be aware of the cannotInterpret: experiments ?
Sven Van Caekenberghe wrote:
On 08 Feb 2012, at 11:42, Schwab,Wilhelm K wrote:
Ok, but what about 1.3? Is 1.4 "ready" - last word was to use 1.3, which has
some troubles too.
Active Pharo development is happing on the unstable branch, 1.4.
Pharo 1.3 was released a long time ago, as
Stef,
There are things in 1.4 that I will eventually like, but for now, it is very
difficult to use. I had a code holder get dragged and dropped from a browser
to the desktop and couldn't get a halo to kill it. Context menus don't work
well and lack the polish of earlier versions.
My problem
Frank Shearar wrote:
On 8 February 2012 10:33, Norbert Hartl wrote:
Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
On 02/08/2012 10:43 AM, Marcus Denker wrote:
On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
well I do not think so since we can all read the
On Tue, Feb 7, 2012 at 11:52 PM, Benjamin <
benjamin.vanryseghem.ph...@gmail.com> wrote:
> For traits method, you have this nice icon ^^
>
>
What about hiding the methods coming from the traits? We don't show the
methods coming from superclasses so I don't see any reason why methods
coming from t
1.4 is stable but we are working on it.
STef
On Feb 8, 2012, at 11:42 AM, Schwab,Wilhelm K wrote:
> Ok, but what about 1.3? Is 1.4 "ready" - last word was to use 1.3, which has
> some troubles too.
>
>
>
>
>
> From: pharo-project-boun...@lists.gforge
Well the main thing here is that I still have to manually create the project on
gemstone :P
On 2012-02-07, at 20:55, Dale Henrichs wrote:
> Ben,
>
> I think that Mariano describes what you are looking for[1]
>
> [1]
> http://marianopeck.wordpress.com/2011/11/08/migrating-projects-to-squeakso
Well, it's the turtles all the way down, and you always need a peace of trust
to step on to keep the whole thing. So there is no absulute security, but I
guess this is not a new concept.
But IMHO, if someone would like to reduce (not eliminate) the risks,
Smalltalk could make it less daunting. Sma
Am 08.02.2012 um 12:04 schrieb Philippe Marschall:
> On 02/08/2012 11:33 AM, Norbert Hartl wrote:
>>
>> Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
>>
>>> On 02/08/2012 10:43 AM, Marcus Denker wrote:
On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
>> well I do
On 02/08/2012 11:33 AM, Norbert Hartl wrote:
Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
On 02/08/2012 10:43 AM, Marcus Denker wrote:
On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
well I do not think so since we can all read the code.
No, read the argument again. If the c
Hi Laurent!
Thanks for the response, and don't worry, nothing urgent.
Let me know if I can help, and yes, count me as a potential user.
Cheers.
2012/2/8 laurent laffont
> Hi German,
>
> at least one potential user :)
>
> I'll have a look this week, still not have totally recovered from FOSDE
On 08 Feb 2012, at 11:42, Schwab,Wilhelm K wrote:
> Ok, but what about 1.3? Is 1.4 "ready" - last word was to use 1.3, which has
> some troubles too.
Active Pharo development is happing on the unstable branch, 1.4.
Pharo 1.3 was released a long time ago, as a freeze of the development branch,
On 8 February 2012 10:33, Norbert Hartl wrote:
>
> Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
>
>> On 02/08/2012 10:43 AM, Marcus Denker wrote:
>>>
>>> On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
>>>
> well I do not think so since we can all read the code.
No, read
Ok, but what about 1.3? Is 1.4 "ready" - last word was to use 1.3, which has
some troubles too.
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Marcus Denker
[marcus.den...@inria.fr]
Sent:
Am 08.02.2012 um 11:12 schrieb Philippe Marschall:
> On 02/08/2012 10:43 AM, Marcus Denker wrote:
>>
>> On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
>>
well I do not think so since we can all read the code.
>>>
>>> No, read the argument again. If the compiler is compromised and
On Feb 8, 2012, at 11:22 AM, Schwab,Wilhelm K wrote:
> Stef,
>
> We are on the same topic then. I am having problems with cmd . on 1.3 - it
> won't break anything :(
>
it is fixed in 1.4.
Marcus
--
Marcus Denker -- http://marcusdenker.de
Stef,
We are on the same topic then. I am having problems with cmd . on 1.3 - it
won't break anything :(
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Stéphane Ducasse
[stephane.duca
The idea is that most of the time when you pressed cmd . you killed stopped
either
the UI of the debugger you were invoking :) or the finalization process. too
bad… you stopped the only guy that
was helping you to receiver from memory. No such process are not selected when
you press . cmd
On
On 02/08/2012 10:43 AM, Marcus Denker wrote:
On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
well I do not think so since we can all read the code.
No, read the argument again. If the compiler is compromised and the other tools
in the image are compromised you can't read the code bec
On Feb 8, 2012, at 10:39 AM, Philippe Marschall wrote:
>> well I do not think so since we can all read the code.
>
> No, read the argument again. If the compiler is compromised and the other
> tools in the image are compromised you can't read the code because the tools
> don't display you the
On 02/08/2012 10:33 AM, Stéphane Ducasse wrote:
On Feb 8, 2012, at 9:35 AM, Philippe Marschall wrote:
On 02/07/2012 02:47 PM, Ben Coman wrote:
This is slightly paranoid thinking, but considering the long evolution
of Smalltalk live images (apparently all the way from the original Xerox
PARC
On Feb 8, 2012, at 9:35 AM, Philippe Marschall wrote:
> On 02/07/2012 02:47 PM, Ben Coman wrote:
>>
>> This is slightly paranoid thinking, but considering the long evolution
>> of Smalltalk live images (apparently all the way from the original Xerox
>> PARC ST80 [1] ) in relation to Ken Thompson
For the rest of us, fixed what, when? Just curious.
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Sven Van
Caekenberghe [s...@beta9.be]
Sent: Wednesday, February 08, 2012 3:01 AM
To: Pharo-
On 02/07/2012 02:47 PM, Ben Coman wrote:
This is slightly paranoid thinking, but considering the long evolution
of Smalltalk live images (apparently all the way from the original Xerox
PARC ST80 [1] ) in relation to Ken Thompson's "Reflections on Trusting
Trust" [2] - are there any mechanisms to
On 07 Feb 2012, at 23:34, Benjamin wrote:
> This version introduce:
> - a lot of bug fixes
> - a better comment pane
> - speed increased by 10 (thanks to Camillo)
Super, getting better all the time!
> Hope you will enjoy it :)
Yes.
Sven
Sig en Co,
Thanks a lot for the fixed interrupt behavior !
It worked perfectly.
This really makes a difference.
Sven
40 matches
Mail list logo
