On 31 May 2013 09:00, Norbert Hartl wrote:
>
>
> Am 31.05.2013 um 02:56 schrieb Igor Stasenko :
>
>> ohohoho.. selector namespaces.. sounds like using nuclear weapon to
>> get rid of cockroaches:
>
> You know that cockroaches are the ones that will survive a nuclear strike ? :)
>
yes, i know. And
Am 31.05.2013 um 02:56 schrieb Igor Stasenko :
> ohohoho.. selector namespaces.. sounds like using nuclear weapon to
> get rid of cockroaches:
You know that cockroaches are the ones that will survive a nuclear strike ? :)
Norbert
On 30 May 2013 21:02, Stéphane Ducasse wrote:
>
>> I don't see the point. Overrides are not an executable concept, they are a
>> package management concept. At execution, only methods do exist. How two
>> overrides (or even one method and one override) work are the duty of the
>> package manage
> I don't see the point. Overrides are not an executable concept, they are a
> package management concept. At execution, only methods do exist. How two
> overrides (or even one method and one override) work are the duty of the
> package management system.
yes :)
> If the package management sy
For marcus and igor.
Now when we work on the core you have some methods with some behavior and since
you
want to have a small kernel you define some methods in a certain way.
Now after you want to load code on top and suddenly you want to change the
behavior to use the loaded package. And I
On 29 May 2013 09:07, Marcus Denker wrote:
>
> On May 29, 2013, at 9:04 AM, Goubier Thierry wrote:
>
>> Le 28/05/2013 22:23, stephane ducasse a écrit :
>>>
>>>
I have a question about RPackage and overrides.
RPackage consider that an override method is an extension, right?
>>>
>>>
Le 30/05/2013 14:27, Marcus Denker a écrit :
On May 30, 2013, at 2:22 PM, Goubier Thierry wrote:
Le 30/05/2013 14:09, Stéphane Ducasse a écrit :
On May 30, 2
Yes. I can say true become: false, too.
Overrides can be interesting as a temperer hack. E.g. in Opal development, I
might add an
On May 30, 2013, at 2:22 PM, Goubier Thierry wrote:
> Le 30/05/2013 14:09, Stéphane Ducasse a écrit :
>>
>> On May 30, 2
>>> Yes. I can say true become: false, too.
>>>
>>> Overrides can be interesting as a temperer hack. E.g. in Opal development,
>>> I might add an override just to test. The
Le 30/05/2013 14:09, Stéphane Ducasse a écrit :
On May 30, 2
Yes. I can say true become: false, too.
Overrides can be interesting as a temperer hack. E.g. in Opal development, I
might add an override just to test. Then loading Opal makes
the image package dirty. So later, when I know what I w
On May 30, 2
> Yes. I can say true become: false, too.
>
> Overrides can be interesting as a temperer hack. E.g. in Opal development, I
> might add an override just to test. Then loading Opal makes
> the image package dirty. So later, when I know what I want, I will move that
> change to the im
On May 30, 2013, at 9:44 AM, Goubier Thierry wrote:
> Le 29/05/2013 23:16, stephane ducasse a écrit :
>>
>> On May 29, 2013, at 9:08 AM, Goubier Thierry wrote:
>>
>>> Le 28/05/2013 22:23, stephane ducasse a écrit :
> I have a question about RPackage and overrides.
>
>
Le 29/05/2013 23:16, stephane ducasse a écrit :
On May 29, 2013, at 9:08 AM, Goubier Thierry wrote:
Le 28/05/2013 22:23, stephane ducasse a écrit :
I have a question about RPackage and overrides.
RPackage consider that an override method is an extension, right?
for RPackage a package i
On May 29, 2013, at 9:08 AM, Goubier Thierry wrote:
> Le 28/05/2013 22:23, stephane ducasse a écrit :
>>
>>
>>> I have a question about RPackage and overrides.
>>>
>>> RPackage consider that an override method is an extension, right?
>>
>> for RPackage a package is a list of method definitio
Le 29/05/2013 14:39, Sean P. DeNigris a écrit :
Goubier Thierry wrote
So, what do we do ?
Maybe create an issue with "later" milestone pointing to this discussion?
Done.
https://pharo.fogbugz.com/default.asp?10790
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes
Goubier Thierry wrote
> So, what do we do ?
Maybe create an issue with "later" milestone pointing to this discussion?
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Pharo-dev-RPackage-and-overrides-tp4690435p4690606.html
Sent from the Pharo Smallta
On May 29, 2013, at 9:17 AM, Goubier Thierry wrote:
> Le 29/05/2013 09:07, Marcus Denker a écrit :
>>
>> On May 29, 2013, at 9:04 AM, Goubier Thierry wrote:
>>
>>> Le 28/05/2013 22:23, stephane ducasse a écrit :
> I have a question about RPackage and overrides.
>
> RP
Le 29/05/2013 09:07, Marcus Denker a écrit :
On May 29, 2013, at 9:04 AM, Goubier Thierry wrote:
Le 28/05/2013 22:23, stephane ducasse a écrit :
I have a question about RPackage and overrides.
RPackage consider that an override method is an extension, right?
for RPackage a package is a
On May 29, 2013, at 9:04 AM, Goubier Thierry wrote:
> Le 28/05/2013 22:23, stephane ducasse a écrit :
>>
>>
>>> I have a question about RPackage and overrides.
>>>
>>> RPackage consider that an override method is an extension, right?
>>
>> for RPackage a package is a list of method definitio
Le 28/05/2013 22:23, stephane ducasse a écrit :
I have a question about RPackage and overrides.
RPackage consider that an override method is an extension, right?
for RPackage a package is a list of method definitions and class definition.
There is no specific tagging for overriding methods
> I have a question about RPackage and overrides.
>
> RPackage consider that an override method is an extension, right?
for RPackage a package is a list of method definitions and class definition.
There is no specific tagging for overriding methods that would magically
reappear when
their over
I have a question about RPackage and overrides.
RPackage consider that an override method is an extension, right?
What would be the difference between an extension and an override, apart
from the protocol name? Is it usefull to have a difference? (i.e. if you
missclassify a method between exte
21 matches
Mail list logo