then use rebol and not Smalltalk. But do not imagine that Smalltalk
will be rebol.
Stéphane Ducasse wrote:
No it should follow well specified rules.
Ultimately the compiler is not really compiling smalltalk, it is
compiling some primitive concepts that Behaviour and friends turn in
to
Yes this is the question and the effort to be different.
I always thought this constraint was because of an optimization
in early days such as been able to depop without taking care.
Stef
On Dec 24, 2008, at 10:58 AM, br...@kampjes.demon.co.uk
br...@kampjes.demon.co.uk
wrote:
Stéphane
On Wed, Dec 24, 2008 at 10:58 AM, br...@kampjes.demon.co.uk wrote:
This is a language design point. Is the convenience of knowing that
an argument is never modified worth more than the convenience of being
able to modify the argument?
What really is the convenience of modifying an argument?
Yes, that's the point.
2008/12/24 Michael Rueger m.rue...@acm.org:
Breaking the kind of conventions makes you think harder about what
code does and that distracts you from what you really trying to do. Or
should be doing ;-)
___
Pharo-project
Stéphane Ducasse writes:
In that case we could change that. But then we would produce
incompatible code
also.
Compatibility is less of an issue for this change as Pharo will accept
more code rather than less. It will not stop us importing any code
that currently runs on Squeak unlike
+1
even if I understand since from time to time I need to add a new local
to modify an
arg. Now I have the impression that when I have to do that it may be
better to
have an instance variable instead.
Stef
On Dec 24, 2008, at 11:11 AM, Michael Rueger wrote:
On Wed, Dec 24, 2008 at 10:58
At Thu, 18 Dec 2008 19:55:31 +0100,
Stéphane Ducasse wrote:
On Dec 18, 2008, at 6:34 PM, Lukas Renggli wrote:
I've discussed with Stephane and may be we can fix all the methods
that have :
_ instead of :=
or some methods have [ :myArg ... ] instead of [ :myArg ]
I
to: stop by: step
...
[ : stop : step | ... ]
It looks a weak argument to me :)
I would hate to teach that.
I neither thought you could even do that.
Just for the record, what Lukas described (the part where the args
to block should look like keyword-less keyword
Michael Rueger wrote:
On Wed, Dec 24, 2008 at 10:58 AM, br...@kampjes.demon.co.uk wrote:
This is a language design point. Is the convenience of knowing that
an argument is never modified worth more than the convenience of being
able to modify the argument?
What really is the
It depends whether it makes sense or not to have a different threshold
for objects.
Maybe an expert in gui may help to answer this...
Alexandre
On 23 Dec 2008, at 19:19, Stéphane Ducasse wrote:
Hi
I would like to get your point of view on the following:
In Object there is the method
On Wed, Dec 24, 2008 at 12:30 PM, Keith Hodges keith_hod...@yahoo.co.uk wrote:
I am not saying that the smalltalk conventions are bad, what I am saying
is that the flexibility to break the conventions is useful in OTHER
CONTEXTS, and in many ways makes it possible to have other use cases in
Dear List,
Before we have the Mac menu, Cmd-Q was completing a symbol being
written. Is there a new mapping for this?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Adding 'Beeper beep' in the body of these two empty methods does not
produce any sound. This is normal since methods that use these methods
are primitive. Now, we could remove these two methods from Object, but
it would be wise to leave the calls in the body of primitive methods.
Could be a
I am not sure about what Christo needs exactly. When I load Christo,
Gepetto2 is loaded. I therefore assume that the former needs the latter.
Alexandre
On 23 Dec 2008, at 19:07, Stéphane Ducasse wrote:
Marcus
You were talking about reflectivity but alex about bytesurgeon.
Is geppetto2 =
yes but so far none of the moprh class specialised this method.
On Dec 24, 2008, at 2:00 PM, Alexandre Bergel wrote:
It depends whether it makes sense or not to have a different threshold
for objects.
Maybe an expert in gui may help to answer this...
Alexandre
On 23 Dec 2008, at 19:19,
I will wait that somebody with VM building knowledge reply. I imagine
that these
two methods are handy when you want to debug a primitive in Squeak
before generating C code.
Stef
On Dec 24, 2008, at 2:10 PM, Alexandre Bergel wrote:
Adding 'Beeper beep' in the body of these two empty methods
Ok I thought I saw an BS packagein the repo
On Dec 24, 2008, at 2:14 PM, Alexandre Bergel wrote:
I am not sure about what Christo needs exactly. When I load Christo,
Gepetto2 is loaded. I therefore assume that the former needs the
latter.
Alexandre
On 23 Dec 2008, at 19:07, Stéphane
Michael Rueger wrote:
On Wed, Dec 24, 2008 at 12:30 PM, Keith Hodges keith_hod...@yahoo.co.uk
wrote:
I am not saying that the smalltalk conventions are bad, what I am saying
is that the flexibility to break the conventions is useful in OTHER
CONTEXTS, and in many ways makes it possible
I think that this is the morph scheduler model that is wrong.
but unfortunately I'm not good enough in concurrent programming to
fix. I remember that once nathanael told me that it was bogus by
construction
and that he understood how to do a good one. Too bad google took him :)
On Dec 24, 2008,
On Wed, Dec 24, 2008 at 15:13, Alexandre Bergel alexan...@bergel.eu wrote:
I do not think that a preference should relax some static language
enforcements.
Rule of thumb: if you just thought maybe a preference would fix
that… then you're avoiding the real problem :)
I think the initial concern
Yes I contacted Janko if he can fix that
On Dec 24, 2008, at 5:25 PM, Damien Pollet wrote:
On Wed, Dec 24, 2008 at 15:13, Alexandre Bergel
alexan...@bergel.eu wrote:
I do not think that a preference should relax some static language
enforcements.
Rule of thumb: if you just thought maybe
http://code.google.com/p/pharo/issues/detail?id=226
http://code.google.com/p/pharo/issues/detail?id=368 ( which lead to
http://code.google.com/p/pharo/issues/detail?id=173 )
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
On Wed, Dec 24, 2008 at 19:43, Damien Pollet damien.pol...@gmail.com wrote:
PS. After re-reading Lukas's mails, Transcript and Workspace do work here too
:)
Actually, after implementing String classspace, most windows worked ;)
--
Damien Pollet
type less, do more [ | ]
I like to see your emails coming in :)
I will look at that and integrate them. Merry sunny christmax
here this is cold :)
Stef
On Dec 24, 2008, at 7:45 PM, Hernán Morales Durand wrote:
http://code.google.com/p/pharo/issues/detail?id=226
just to share that with you
Begin forwarded message:
From: Daniel Ingalls dan.inga...@sun.com
Date: December 24, 2008 8:48:09 PM CEST
To: Stéphane Ducasse stephane.duca...@inria.fr
Subject: Re: A little question --- merry christmas
Hi, Stef -
Merry chrismas for you and your family.
and
Ok, well the ugly part of this is that we have some Slang in the base
pharo, either as Slang code or doubling as primitive failure recovery
code .
Normally if we had say:
primAddActiveEdgeTableEntryFrom: edgeEntry
Add edge entry to the AET.
primitive:
Stef,
It was not until I re-read this that I took note of just who had all this great
insight into computing. I fully agree about the debugging benefits of
immutable arguments. The same argument leads me to want to avoid name
collisions between temporary and instance variables.
Please tell
27 matches
Mail list logo
