Hi
is there a way to see in the browse all the methods implemented in the super
classes as well, maybe in a different colour,
i thought it was possible but am unable to find it
regards
Sanjay
-
---
Regards, Sanjay
--
View this message in context:
http://forum.world.st/how-to-see-method
Should be fine now
On 14 May 2015 at 17:54, Cyril Ferlicot wrote:
> I'll make a new configuration un few hours
>
>
> Le jeudi 14 mai 2015, Alexandre Bergel a écrit :
>>
>> Hi!
>>
>> When I load Pillar, I have the following:
>> This package depends on the following classes:
>> PRWarning
>> You
Pierre Chanson wrote
> I had a bug...
Issue 15540: Finder Should Accept Run-Time Arrays
https://pharo.fogbugz.com/default.asp?15540
I traced the problem to Finder>>findSelector:, which uses #parseLiterals,
but:
'{1. 2}' parseLiterals. "#(#'{' 1 #'.' 2 #'}')"
'#(1 2)' parseLiterals. "#(#(1 2))"
Pierre Chanson wrote
> this one is not
> {'bc'. 'ab'}..{'ab'. 'bc'}
Interestingly, `#('bc' 'ab').{'ab'. 'bc'}` works
N.B. in general you can leave out the extra $.
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Wait-two-seconds-tp4825675p4826362.html
Sent from the P
Hi there,
I really liked the video, sent it to a friend to convince him to try
Pharo... It also remind me that there is this really nice tool, the finder.
Sadly, on the first try I had a bug:
this request by example is working
#('bc' 'ab')..#('ab' 'bc')
this one is not
{'bc'. 'ab'}..{'ab'. 'bc'}
I'll make a new configuration un few hours
Le jeudi 14 mai 2015, Alexandre Bergel a écrit :
> Hi!
>
> When I load Pillar, I have the following:
> This package depends on the following classes:
> PRWarning
> You must resolve these dependencies before you will be able to load these
> definitions
Hi!
When I load Pillar, I have the following:
This package depends on the following classes:
PRWarning
You must resolve these dependencies before you will be able to load these
definitions:
PRParameterWarning
I simply do
-=-=-=-=-=-=-=-=-=
Gofer new
smalltalkhubUser: 'Pier' project:
Back in the time of ModularSmalltalk and S#, we had fierce discussions on a
symbol resolution to implement selector namespaces. We had something like that:
Symbol + Namespace = selector
As a result, several namespaces could define a method with the same selector on
a same class, thus avoiding c