Object>>at:modify:???

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Object>>at:modify:???

stephane ducasse
I would like to deprecate the following method since nobody use it.
What do you think?

Stef

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Hernan Wilkinson-3
In a 1.1 image I have, the class HttpRequest is using that message...

On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
I would like to deprecate the following method since nobody use it.
What do you think?

Stef

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
Hernán Wilkinson
Agile Software Development, Teaching & Coaching
Mobile: +54 - 911 - 4470 - 7207
email: [hidden email]
site: http://www.10Pines.com


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Philippe Marschall-2-3
On 22.10.2010 23:04, Hernan Wilkinson wrote:
> In a 1.1 image I have, the class HttpRequest is using that message...

At least we should move it to Dictionary. But I think we can easily fix Kom.

Cheers
Philippe


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Stéphane Ducasse
In reply to this post by stephane ducasse
Ok we can deprecate it.

On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:

> In a 1.1 image I have, the class HttpRequest is using that message...
>
> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
> I would like to deprecate the following method since nobody use it.
> What do you think?
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> Hernán Wilkinson
> Agile Software Development, Teaching & Coaching
> Mobile: +54 - 911 - 4470 - 7207
> email: [hidden email]
> site: http://www.10Pines.com
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Mariano Martinez Peck


On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse <[hidden email]> wrote:
Ok we can deprecate it.


ys, but please please please use deprecated: anExplanationString on: date in: version

cheers

mariano
 
On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:

> In a 1.1 image I have, the class HttpRequest is using that message...
>
> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
> I would like to deprecate the following method since nobody use it.
> What do you think?
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> Hernán Wilkinson
> Agile Software Development, Teaching & Coaching
> Mobile: +54 - 911 - 4470 - 7207
> email: [hidden email]
> site: http://www.10Pines.com
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Guillermo Polito
Why not deprecate/remove the #deprecate: without the useful parameters? :D

2010/10/23 Mariano Martinez Peck <[hidden email]>


On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse <[hidden email]> wrote:
Ok we can deprecate it.


ys, but please please please use deprecated: anExplanationString on: date in: version

cheers

mariano
 
On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:

> In a 1.1 image I have, the class HttpRequest is using that message...
>
> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
> I would like to deprecate the following method since nobody use it.
> What do you think?
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> Hernán Wilkinson
> Agile Software Development, Teaching & Coaching
> Mobile: +54 - 911 - 4470 - 7207
> email: [hidden email]
> site: http://www.10Pines.com
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Stéphane Ducasse
In reply to this post by Mariano Martinez Peck
yes we probably should

On Oct 23, 2010, at 4:04 PM, Guillermo Polito wrote:

> Why not deprecate/remove the #deprecate: without the useful parameters? :D
>
> 2010/10/23 Mariano Martinez Peck <[hidden email]>
>
>
> On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse <[hidden email]> wrote:
> Ok we can deprecate it.
>
>
> ys, but please please please use deprecated: anExplanationString on: date in: version
>
> cheers
>
> mariano
>  
> On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:
>
> > In a 1.1 image I have, the class HttpRequest is using that message...
> >
> > On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
> > I would like to deprecate the following method since nobody use it.
> > What do you think?
> >
> > Stef
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [hidden email]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
> >
> >
> > --
> > Hernán Wilkinson
> > Agile Software Development, Teaching & Coaching
> > Mobile: +54 - 911 - 4470 - 7207
> > email: [hidden email]
> > site: http://www.10Pines.com
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [hidden email]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Mariano Martinez Peck
In reply to this post by Guillermo Polito


2010/10/23 Guillermo Polito <[hidden email]>
Why not deprecate/remove the #deprecate: without the useful parameters? :D

2010/10/23 Mariano Martinez Peck <[hidden email]>



On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse <[hidden email]> wrote:
Ok we can deprecate it.


ys, but please please please use deprecated: anExplanationString on: date in: version

cheers

mariano
 
On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:

> In a 1.1 image I have, the class HttpRequest is using that message...
>
> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <[hidden email]> wrote:
> I would like to deprecate the following method since nobody use it.
> What do you think?
>
> Stef
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
> --
> Hernán Wilkinson
> Agile Software Development, Teaching & Coaching
> Mobile: +54 - 911 - 4470 - 7207
> email: [hidden email]
> site: http://www.10Pines.com
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Object>>at:modify:???

Philippe Marschall-2-3
In reply to this post by Philippe Marschall-2-3
On 23.10.2010 14:23, Philippe Marschall wrote:
> On 22.10.2010 23:04, Hernan Wilkinson wrote:
>> In a 1.1 image I have, the class HttpRequest is using that message...
>
> At least we should move it to Dictionary. But I think we can easily fix Kom.

It's gone in KomHttpServer-pmm.60

Cheers
Philippe


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Deprecation policy (was: Re: Object>>at:modify:???)

Levente Uzonyi-2
In reply to this post by Mariano Martinez Peck
On Sat, 23 Oct 2010, Mariano Martinez Peck wrote:

> On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse <[hidden email]
>> wrote:
>
>> Ok we can deprecate it.
>>
>>
> ys, but please please please use deprecated: anExplanationString on: date
> in: version

Wouldn't it be easier to rely on method timestamps + a version cache, than
spreading redundant information all over the place? Something like:

Object >> deprecated: anExplanationString
  "Warn that the sending method has been deprecated."

  (Deprecation
  method: thisContext sender method
  explanation: anExplanationString
  on: (TimeStamp fromMethodTimeStamp: thisContext sender method timeStamp) date "Or something nicer") signal

Deprecation class >> method: aCompiledMethod explanation: anExplanationString on: date

  ^self new
  method: aCompiledMethod
  explanation: anExplanationString
  on: date asString
  in: (SystemVersion alphaVersionAt: date)

Someone has to implement #alphaVersionAt: (which is easy,  but
SystemVersion has to be modified).
Finally the developement process has to follow some simple rules.


Levente

>
> cheers
>
> mariano
>
>
>> On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:
>>
>>> In a 1.1 image I have, the class HttpRequest is using that message...
>>>
>>> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <
>> [hidden email]> wrote:
>>> I would like to deprecate the following method since nobody use it.
>>> What do you think?
>>>
>>> Stef
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>>
>>> --
>>> Hernán Wilkinson
>>> Agile Software Development, Teaching & Coaching
>>> Mobile: +54 - 911 - 4470 - 7207
>>> email: [hidden email]
>>> site: http://www.10Pines.com
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Deprecation policy (was: Re: Object>>at:modify:???)

Michael Roberts-2
I think the idea was that the deprecation scheme was fairly simple,
and slightly better than just the original deprecated: . What you
describe looks a bit over the top to me.  just my 2p...

cheers,
Mike

2010/10/24 Levente Uzonyi <[hidden email]>:

> On Sat, 23 Oct 2010, Mariano Martinez Peck wrote:
>
>> On Sat, Oct 23, 2010 at 1:32 PM, Stéphane Ducasse
>> <[hidden email]
>>>
>>> wrote:
>>
>>> Ok we can deprecate it.
>>>
>>>
>> ys, but please please please use deprecated: anExplanationString on: date
>> in: version
>
> Wouldn't it be easier to rely on method timestamps + a version cache, than
> spreading redundant information all over the place? Something like:
>
> Object >> deprecated: anExplanationString
>        "Warn that the sending method has been deprecated."
>
>        (Deprecation
>                method: thisContext sender method
>                explanation: anExplanationString
>                on: (TimeStamp fromMethodTimeStamp: thisContext sender method
> timeStamp) date "Or something nicer") signal
>
> Deprecation class >> method: aCompiledMethod explanation:
> anExplanationString on: date
>
>        ^self new
>                method: aCompiledMethod
>                explanation: anExplanationString
>                on: date asString
>                in: (SystemVersion alphaVersionAt: date)
>
> Someone has to implement #alphaVersionAt: (which is easy,  but SystemVersion
> has to be modified).
> Finally the developement process has to follow some simple rules.
>
>
> Levente
>
>>
>> cheers
>>
>> mariano
>>
>>
>>> On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote:
>>>
>>>> In a 1.1 image I have, the class HttpRequest is using that message...
>>>>
>>>> On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <
>>>
>>> [hidden email]> wrote:
>>>>
>>>> I would like to deprecate the following method since nobody use it.
>>>> What do you think?
>>>>
>>>> Stef
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>>
>>>>
>>>> --
>>>> Hernán Wilkinson
>>>> Agile Software Development, Teaching & Coaching
>>>> Mobile: +54 - 911 - 4470 - 7207
>>>> email: [hidden email]
>>>> site: http://www.10Pines.com
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project