Re: [gobo-eiffel-develop] ET_AST_ITERATOR.process_features

[Eric B. <er...@go...>]

Howard Thomson wrote:
> I don't yet fully understand the implications of the presence of synonyms in a 
> class,

The trick is that the ET_AST_PRINTER prints:

    foo, bar (...) is
        do
           ...
        end

and not:

    foo (...) is
        do
           ...
        end

    bar (...) is
        do
           ...
        end

when it finds synonyms. This is needed when what we want it just
change the formating of a class text without decoupling synonym
features. This trick about synonyms is done if class ET_AST_ITERATOR
in feature `process_features' and for example in feature
`process_do_procedure'. If you don't want this behavior and want
the synonym features to stand by themsleves, then you would need
to redefine these features in a descendant of ET_AST_PRINTER.

> and I am unsure as to what assumptions one can make about the ordering 
> of features in ET_CLASS.queries and ET_CLASS.procedures.

Queries in ET_CLASS.queries between 1 and `queries.declared_count' are
guaranteed to be sorted in the order they appear in the class text.
Likewise for procedures. However we know nothing about the ordering
between a query and a procedure. We have to compare their position
in the class text in that case.

-- 
Eric Bezault
mailto:er...@go...
http://www.gobosoft.com