flags in pharo

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

flags in pharo

Thibault ARLOING

Hi,


Can someone explain me how ProtoObject>>flag: works in pharo please ?


thx,


Thibault Arloing

Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Damien Pollet-2
It's just an empty method doing nothing.

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,


Can someone explain me how ProtoObject>>flag: works in pharo please ?


thx,


Thibault Arloing


Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Marcus Denker-4
Hi,

the convention is to put something like

self flag: #TODO.

in the code, then you can search for senders of #TODO and get a list of all things you wanted to fix.

Marcus


On 06 Apr 2016, at 14:17, Damien Pollet <[hidden email]> wrote:

It's just an empty method doing nothing.

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,


Can someone explain me how ProtoObject>>flag: works in pharo please ?


thx,


Thibault Arloing



Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Thibault ARLOING

Ok, but i understand that it can't be use to know if we already pass through a method ?


Thibault



De : Pharo-users <[hidden email]> de la part de Marcus Denker <[hidden email]>
Envoyé : mercredi 6 avril 2016 14:25
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo
 
Hi,

the convention is to put something like

self flag: #TODO.

in the code, then you can search for senders of #TODO and get a list of all things you wanted to fix.

Marcus


On 06 Apr 2016, at 14:17, Damien Pollet <[hidden email]> wrote:

It's just an empty method doing nothing.

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,


Can someone explain me how ProtoObject>>flag: works in pharo please ?


thx,


Thibault Arloing



Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Blondeau Vincent

No, it is just a marker for the method.

 

If you want to do what you asked, put a halt (self halt), or, a trace (self crLog: ‘amessage’) and open the Transcript.

 

Vincent

 

De : Pharo-users [mailto:[hidden email]] De la part de Thibault ARLOING
Envoyé : mercredi 6 avril 2016 14:44
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Ok, but i understand that it can't be use to know if we already pass through a method ?

 

Thibault

 


De : Pharo-users <[hidden email]> de la part de Marcus Denker <[hidden email]>
Envoyé : mercredi 6 avril 2016 14:25
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Hi,

 

the convention is to put something like

 

self flag: #TODO.

 

in the code, then you can search for senders of #TODO and get a list of all things you wanted to fix.

 

Marcus

 

 

On 06 Apr 2016, at 14:17, Damien Pollet <[hidden email]> wrote:

 

It's just an empty method doing nothing.

 

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

 

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,

 

Can someone explain me how ProtoObject>>flag: works in pharo please ?

 

thx,

 

Thibault Arloing

 

 


!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"
Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

philippeback

On Wed, Apr 6, 2016 at 2:47 PM, Blondeau Vincent <[hidden email]> wrote:

No, it is just a marker for the method.

 

If you want to do what you asked, put a halt (self halt), or, a trace (self crLog: ‘amessage’) and open the Transcript.


You may want to investigate MethodWrappers: http://scg.unibe.ch/wiki/faq/pharo/howToLoadMethodWrappers



This for sure will help in achieving what you want.

HTH
Phil

 

 

Vincent

 

De : Pharo-users [mailto:[hidden email]] De la part de Thibault ARLOING
Envoyé : mercredi 6 avril 2016 14:44
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Ok, but i understand that it can't be use to know if we already pass through a method ?

 

Thibault

 


De : Pharo-users <[hidden email]> de la part de Marcus Denker <[hidden email]>
Envoyé : mercredi 6 avril 2016 14:25
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Hi,

 

the convention is to put something like

 

self flag: #TODO.

 

in the code, then you can search for senders of #TODO and get a list of all things you wanted to fix.

 

Marcus

 

 

On 06 Apr 2016, at 14:17, Damien Pollet <[hidden email]> wrote:

 

It's just an empty method doing nothing.

 

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

 

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,

 

Can someone explain me how ProtoObject>>flag: works in pharo please ?

 

thx,

 

Thibault Arloing

 

 


!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Thibault ARLOING

I finally found want i search, so the flags were not useful !

i just wanted to know, in a method, if i already pass through the previous method.

I just have to transport an additional information.


thank you for your answer, they help me in finding the solution :)


Thibault



De : Pharo-users <[hidden email]> de la part de [hidden email] <[hidden email]>
Envoyé : mercredi 6 avril 2016 15:35
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo
 

On Wed, Apr 6, 2016 at 2:47 PM, Blondeau Vincent <[hidden email]> wrote:

No, it is just a marker for the method.

 

If you want to do what you asked, put a halt (self halt), or, a trace (self crLog: ‘amessage’) and open the Transcript.


You may want to investigate MethodWrappers: http://scg.unibe.ch/wiki/faq/pharo/howToLoadMethodWrappers



This for sure will help in achieving what you want.

HTH
Phil

 

 

Vincent

 

De : Pharo-users [mailto:[hidden email]] De la part de Thibault ARLOING
Envoyé : mercredi 6 avril 2016 14:44
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Ok, but i understand that it can't be use to know if we already pass through a method ?

 

Thibault

 


De : Pharo-users <[hidden email]> de la part de Marcus Denker <[hidden email]>
Envoyé : mercredi 6 avril 2016 14:25
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] flags in pharo

 

Hi,

 

the convention is to put something like

 

self flag: #TODO.

 

in the code, then you can search for senders of #TODO and get a list of all things you wanted to fix.

 

Marcus

 

 

On 06 Apr 2016, at 14:17, Damien Pollet <[hidden email]> wrote:

 

It's just an empty method doing nothing.

 

Then, as it says in the comment, you can use the tools to look for it. Nautilus knows to check for it and display a nice icon in the method list.

 

On 6 April 2016 at 13:54, Thibault ARLOING <[hidden email]> wrote:

Hi,

 

Can someone explain me how ProtoObject>>flag: works in pharo please ?

 

thx,

 

Thibault Arloing

 

 


!!!*************************************************************************************
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Damien Cassou-2
Thibault ARLOING <[hidden email]> writes:

> I finally found want i search, so the flags were not useful !
>
> i just wanted to know, in a method, if i already pass through the previous method.
>
> I just have to transport an additional information.

I was starting to be afraid when Phil proposed MethodWrappers :-). I
think you can do much more simple than that.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill

Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

philippeback
Bah, we have MetaLinks now, what's so scary about MethodWrappers?

On Wed, Apr 6, 2016 at 4:08 PM, Damien Cassou <[hidden email]> wrote:
Thibault ARLOING <[hidden email]> writes:

> I finally found want i search, so the flags were not useful !
>
> i just wanted to know, in a method, if i already pass through the previous method.
>
> I just have to transport an additional information.

I was starting to be afraid when Phil proposed MethodWrappers :-). I
think you can do much more simple than that.

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill



Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Ben Coman
In reply to this post by Thibault ARLOING
On Wed, Apr 6, 2016 at 9:59 PM, Thibault ARLOING
<[hidden email]> wrote:
> i just wanted to know, in a method, if i already pass through the previous
> method.

When a method is called very often and putting a halt is not useful, I
sometimes find it useful to do...
   Transcript crShow: thisContext sender printString.

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: flags in pharo

Damien Cassou-2
In reply to this post by philippeback
"[hidden email]" <[hidden email]> writes:

> Bah, we have MetaLinks now, what's so scary about MethodWrappers?

I know what Thibault is trying to achieve, and there is no reason to use
anything like that :-). I can't say more because I want him to find by
himself the simplest solution (and it does not involve metaprogramming).

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill