Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Hello, in Pharo 6.0, there is new annotations/pragmas like "<todo>".
Is there any doc about this? How can I browse all "todos", how can I browse all possible annotations etc.? Thanks! pf |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Open Spotter, type 'todo', scroll to the bottom, under Pragmas, click, a GT inspector opens on all usages
Or type 'todo #p' .. > On 31 May 2017, at 19:19, Petr Fischer <[hidden email]> wrote: > > Hello, in Pharo 6.0, there is new annotations/pragmas like "<todo>". > > Is there any doc about this? How can I browse all "todos", how can I browse all possible annotations etc.? > > Thanks! pf > |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by Petr Fischer
> On 31 May 2017, at 19:19, Petr Fischer <[hidden email]> wrote: > > Hello, in Pharo 6.0, there is new annotations/pragmas like "<todo>”. that’s Pavel’s intromission :) in fact it should be self flag: #todo. the pragma is less intromission with code, but it has to be put in a specific place. Esteban > > Is there any doc about this? How can I browse all "todos", how can I browse all possible annotations etc.? > > Thanks! pf > |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by Petr Fischer
2017-05-31 19:19 GMT+02:00 Petr Fischer <[hidden email]>:
In fact it is not something new. You always able put any flag as pragma or message in your methods to easily find them later. For example you can put <issue: 'this method is not working when arg = 5'>. Then you can find it in spotter by tapping "issue:". With Calypso we can implement special method group "todo" and also class group to show classes which methods has this flag |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by EstebanLM
2017-05-31 19:48 GMT+02:00 Esteban Lorenzano <[hidden email]>: the pragma is less intromission with code, but it has to be put in a specific place. I think Marcus with Ronie extended pragmas to bind them to AST-nodes. It was needed for lowcode if I remember correctly. Maybe we can add it in Pharo 7? |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by Denis Kudriashov
2017-06-01 10:36 GMT+02:00 Denis Kudriashov <[hidden email]>:
I add issue for this Implement method and class groups for #todo |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
In reply to this post by Denis Kudriashov
It would be nice to revisit this direction… we had a number of designs (the one Ronie did was the third one… for 3 different projects…) In addition, we should explore pragmas for variable definitions on the class level. I will add this to my list of things to explore for pharo 7. Marcus
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This would be really great.
Doru > On Jun 1, 2017, at 11:38 AM, Marcus Denker <[hidden email]> wrote: > > >> On 1 Jun 2017, at 10:39, Denis Kudriashov <[hidden email]> wrote: >> >> >> 2017-05-31 19:48 GMT+02:00 Esteban Lorenzano <[hidden email]>: >> the pragma is less intromission with code, but it has to be put in a specific place. >> >> I think Marcus with Ronie extended pragmas to bind them to AST-nodes. It was needed for lowcode if I remember correctly. Maybe we can add it in Pharo 7? > > It would be nice to revisit this direction… we had a number of designs (the one Ronie did was the third one… for 3 different projects…) > > In addition, we should explore pragmas for variable definitions on the class level. > > I will add this to my list of things to explore for pharo 7. > > Marcus ... [show rest of quote] -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them." |
Free forum by Nabble | Edit this page |