Hi Jannik and all,
Laval Jannik a écrit :
> On Oct 29, 2009, at 04:27 , Serge Stinckwich wrote:
>
>> Are you sure, this is not used anywhere ?
>> Sometimes you need to draw a morph with a specific heading.
>>
...
> Now, do you use, sometimes, this functionality in pharoCore ? or do
> you
Thank you.
Note that this test uses recently controversed (TestCase>>#assert:)
with a Block argument.
Maybe you should add the #value everywhere...
Nicolas
2009/10/28 Adrian Lienhard :
> Thanks, Nicolas
>
> We integrated your fix and now it does not fail anymore. Just have to
> remove it from exp
Lukas
I'm not that against the idea proposed by alex.
I think that knowing that a class is abstract is important to have and
this is
not because Smalltalk original language was weak that we could not
define now a clear definition.
I do not like the definition of RB people because I have class th
2009/10/28 Alexandre Bergel :
>> What would be your isAbstract be useful for?
>
> To know whether it is wise to instantiate a class or not
>
> Alexandre
>
I often instantiate Object
marker := Object new.
Nicolas
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http:/
2009/10/28 Stéphane Ducasse :
> Martin
>
> are these changes related to the graphs you sent?
> I will have a look after my hospital check.
> Andres? Nicolas?
> Any feedback?
> Martin I imagine that I can package the changes :)
>
>
> Stef
>
This has been pretty well explained by Martin and Andres.
After-thoughts: my opinion is:
Martin solution is more pragmatical : it is tailored for getting most
improvment with minimal change in system.
But formally, I prefer Andres design for it's clarity.
- I do not like the idea that #identityHash and #primIdentityHash do
behave differently
- #scaledIden
Dennis Schetinin writes:
> stack := self given: #shouldBeEmpty.
> I'd suggest this to be:
>
> stack := self given: [self shouldBeEmpty].
> This way it's easier to follow what happenning, and refactoring can be
> applied.
Refactoring should not be a problem, it treats symbols
> I'm not that against the idea proposed by alex.
I am not against it either.
> I think that knowing that a class is abstract is important to have and
> this is
> not because Smalltalk original language was weak that we could not
> define now a clear definition.
My complaint is more against:
-
2009/10/28 :
> Em 28/10/2009 17:52, Lukas Renggli escreveu:
>
>>
>> >> What would be your isAbstract be useful for?
>> > To know whether it is wise to instantiate a class or not
>
>> That would be a pure guess then. Presumably you will still have to
>> look at the implementation, at the docume
2009/10/29 Adrian Kuhn
> Dennis Schetinin writes:
>
> > stack := self given: #shouldBeEmpty.
> > I'd suggest this to be:
> >
> > stack := self given: [self shouldBeEmpty].
> > This way it's easier to follow what happenning, and refactoring can be
> applied.
>
> Refactoring should
Object does not "contain" any abstract method.
Alexandre
On 29 Oct 2009, at 05:31, Nicolas Cellier wrote:
> 2009/10/28 Alexandre Bergel :
>>> What would be your isAbstract be useful for?
>>
>> To know whether it is wise to instantiate a class or not
>>
>> Alexandre
>>
>
> I often instantiate Ob
2009/10/29 Dennis Schetinin :
> That's right, my mistake. Anyway IMHO using explicit message sends is
> preferable, no?
I think not in this case. It looks more clean and declaratively when
you use symbols here.
___
Pharo-project mailing list
Pharo-proje
2009/10/29 George Herolyants
> 2009/10/29 Dennis Schetinin :
> > That's right, my mistake. Anyway IMHO using explicit message sends is
> > preferable, no?
>
> I think not in this case. It looks more clean and declaratively when
> you use symbols here.
>
Using symbols (i.e. "almost" constants) in
2009/10/29 Dennis Schetinin :
> Using symbols (i.e. "almost" constants) instead of explicitly telling what
> is happenning (sending a message) is more clean?! :) Ok then... (Not sure
> what you mean by "declarative" here)
The message "given:" tells that to you. And by "declarative" I meant
the wa
2009/10/29 George Herolyants
> 2009/10/29 Dennis Schetinin :
> > Using symbols (i.e. "almost" constants) instead of explicitly telling
> what
> > is happenning (sending a message) is more clean?! :) Ok then... (Not
> sure
> > what you mean by "declarative" here)
>
> The message "given:" tells th
... BTW, it's very similar to mocks implementations. The 1-st version was
(as in SMocks) something like:
mock expect: #messageSend.
...
self checkExpectations.
But it's much more intension-revealing and convinient to use mocks another
way (as in Mocketry for example):
[sut doSomethings] checking
2009/10/29 Dennis Schetinin :
> For me it's not clear at all. But this is much more obvious:
>
> stack := self resultOf: [self shouldBeEmpty].
>
So why to use a block then? And stop, why to use "resultOf:"???
>> And by "declarative" I meant
>> the way you specify dependencies between your
2009/10/29 George Herolyants
> 2009/10/29 Dennis Schetinin :
> > For me it's not clear at all. But this is much more obvious:
> >
> > stack := self resultOf: [self shouldBeEmpty].
> >
>
> So why to use a block then? And stop, why to use "resultOf:"???
>
For the same reason the execution
Can someone please explain to me how to run code critic on a single
class or a single package?
I managed to run it (overnight) on Smalltalk. It found 70189 problems,
many of them jaw-dropping. But I would like to focus it on my code!
Andrew__
Hallo,
I have just install and started playing a bit with Pharo today. The
first thing I tried was to take one of my Seaside projects from Squeak
and see if I can get it going in Pharo? Everything went very smoothly,
except for the following annoying problem - which I - rather
embarrassingly - can
On 29 oct. 2009, at 14:37, Andrew P. Black wrote:
Can someone please explain to me how to run code critic on a single
class or a single package?
In short, use refactoring scope (environment browser)
Follow the nice screencast of Lukas
http://www.lukas-renggli.ch/blog/ob-rb-3
I managed to
Em 29/10/2009 08:36, Nicolas Cellier
escreveu:
> 2009/10/28 :
> > Em 28/10/2009 17:52, Lukas Renggli escreveu:
> >
> >>
> >> >> What would be your isAbstract be useful for? To know whether
> >> > it is wise to instantiate a class or not
> >
> >> That would be a pure guess then. Presumably yo
2009/10/29 :
> Em 29/10/2009 08:36, Nicolas Cellier
> escreveu:
>> 2009/10/28 :
>> > Em 28/10/2009 17:52, Lukas Renggli escreveu:
>> >
>> >>
>> >> >> What would be your isAbstract be useful for? To know whether
>> >> > it is wise to instantiate a class or not
>> >
>> >> That would be a pure
Hello, i loaded the
Announcements package from SqS/AXAnnouncements,
there are some tests failing because they explicitly comparing block
closures class to be a BlockContext.
But since new closure compiler, it should be BlockClosure instead.
What is a proper test you think?
isClosure or isBlock?
A
Hi Igor,
I'm not sure but I think the annoucment version that will be included is
there : http://source.lukas-renggli.ch/announcements
Cheers,
2009/10/29 Igor Stasenko
> Hello, i loaded the
> Announcements package from SqS/AXAnnouncements,
>
> there are some tests failing because they explicit
2009/10/29 Cédrick Béler :
> Hi Igor,
> I'm not sure but I think the annoucment version that will be included is
> there : http://source.lukas-renggli.ch/announcements
> Cheers,
>
And packages in that repository is already present in pharo-core image.
But if you look at AXAnnouncements, you can see
This concern was already raised elsewhere, but AXAnnoucnements is a
port of the original announcement implementation and likely a
copyright violation of the owners. The announcements in Pharo are a
minimal clean room MIT implementation coming from OmniBrowser.
Cheers,
Lukas
2009/10/29 Igor Stasen
George Herolyants writes:
> 2009/10/29 Dennis Schetinin :
> > Using symbols (i.e. "almost" constants) instead of explicitly telling what
> > is happenning (sending a message) is more clean?! :) Ok then... (Not sure
> > what you mean by "declarative" here)
>
> The message "given:" tells that to
Lukas Renggli writes:
> > In that case, we could have isAbstractClass or something else. I feel
> > this information is important.
>
> What would be your isAbstract be useful for?
>
> - SUnit will still have to implement its own #isAbstract to decide if
> a class should be runnable or just prov
>> - SUnit will still have to implement its own #isAbstract to decide if
>> a class should be runnable or just provide test templates.
>> - Pier will still have to implement its own #isAbstract to decide
>> if a
>> class should show up in the GUI.
>> - Magritte will still have to implement its ow
Hi -
Has anyone successfully run a newer version of Pharo on either Ubuntu
9.04 or Ubuntu 9.10 64 bit server? When I try to start the command
line simply says "Segmentation fault" and does not emit a stack
trace. The UUIDPlugin is named UUIDPlugin.bak.I am attempting to
use the latest versi
Hi Paul,
I'm using ubuntu 9.10 rc 64 (desktop version) since 7 days without any
problem.
Pharo run out of the box.
I send my dpkg -l result to you in private.
Cheers
Alain
Paul DeBruicker a écrit :
> Hi -
>
> Has anyone successfully run a newer version of Pharo on either Ubuntu
> 9.04 or Ubuntu
Paul,
You may verify if your Linux distribution has core dumping enabled:
# ulimit -c unlimited
and check if the directory where the VM resides is writeable. Once you run
again the VM and see "Segmentation fault (core dumped)", You may search the
dumped core with "file core" and run a gdb on it
Nicolas,
Would you like Martin's approach better if the selector was
#basicIdentityHash instead of #primIdentityHash? Is it a matter of
naming only, or is there something else?
Andres.
Nicolas Cellier wrote:
> After-thoughts: my opinion is:
> Martin solution is more pragmatical : it is tailor
(note that I mentioned Magma just for the sake of illustration for my
argument... I do not know whether either approach will affect it)
Nicolas Cellier wrote:
> 2009/10/28 Stéphane Ducasse :
>
>> Martin
>>
>> are these changes related to the graphs you sent?
>> I will have a look after my hosp
Hi!
Just to make things clear, AXAnnouncements
- is not "a port of the original announcement implementation"
- is (more or less) based on Vassili Bykov's blog
(http://www.cincomsmalltalk.com/userblogs/vbykov/blogView?searchCategory=Announcements%20Framework)
just like the Announcements pack
Andres Valloud wrote:
> Nicolas,
>
> Would you like Martin's approach better if the selector was
> #basicIdentityHash instead of #primIdentityHash? Is it a matter of
> naming only, or is there something else?
>
> Andres.
>
> Nicolas Cellier wrote:
>> After-thoughts: my opinion is:
>> Martin s
37 matches
Mail list logo
