Yes, of course I know about tags. But, they are not used so prominently just yet. For example, take the AST packages:
- AST-Core
- AST-Interpreter-Core
- AST-Interpreter-Extension
- AST-Interpreter-Test
- AST-Tests-Core

Of these, AST-Core does have tags, but the rest are not explicitly related to the AST concept. By using string magic in this case all of these would appear close together.

That is why I used strings instead of tags.

Cheers,
Doru




On Tue, May 20, 2014 at 11:13 AM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi Doru.

Thank you for explanation. On question. We have a construct called ���tag��� on the package level, so we can reason about the parts of the package on object level. Do we really need to go into string parsing?

Uko

On 18 May 2014, at 09:52, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi,

I was asked several times for how the visualization from the Pharo 3.0 announcement was created. I now put together a blog post to explain it:

Cheers,
Doru

--

"Every thing has its own flow"




--
www.tudorgirba.com

"Every thing has its own flow"