gobo-eiffel-develop

[gobo-eiffel-develop] ET_FEATURE.set_feature_clause

[Howard T. <how...@di...>]

Hi Eric,

The problem with ET_AST_ITERATOR.process_features was that the feature_clause 
attribute was Void for the queries and procedures being processed and 
therefore not matching the current feature_clause.

In the parsing process, the current feature is passed as an argument to the 
new_do_procedure / new_do_function etc routines in ET_AST_FACTORY but are not 
used in those routines to do set_feature_clause for that argument.

Having added Result.set_feature_clause to the relevant 8 routines of 
ET_AST_FACTORY, I am now getting features processed.

Cheers,

Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein 

Re: [gobo-eiffel-develop] ET_FEATURE.set_feature_clause

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

Howard Thomson wrote:
> The problem with ET_AST_ITERATOR.process_features was that the feature_clause 
> attribute was Void for the queries and procedures being processed and 
> therefore not matching the current feature_clause.
> 
> In the parsing process, the current feature is passed as an argument to the 
> new_do_procedure / new_do_function etc routines in ET_AST_FACTORY but are not 
> used in those routines to do set_feature_clause for that argument.
> 
> Having added Result.set_feature_clause to the relevant 8 routines of 
> ET_AST_FACTORY, I am now getting features processed.

You should not do that, but use ET_DECORATED_AST_FACTORY instead.
This is what is done in $GOBO/test/tools and in
$GOBO/example/tools/bang2create.

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

Re: [gobo-eiffel-develop] ET_FEATURE.set_feature_clause

[Howard T. <how...@di...>]

Ah yes, of course .... I hadn't noticed that class.

Thanks.

On Wednesday 22 August 2007 13:53, you wrote:
> Howard Thomson wrote:
> > The problem with ET_AST_ITERATOR.process_features was that the
> > feature_clause attribute was Void for the queries and procedures being
> > processed and therefore not matching the current feature_clause.
> >
> > In the parsing process, the current feature is passed as an argument to
> > the new_do_procedure / new_do_function etc routines in ET_AST_FACTORY but
> > are not used in those routines to do set_feature_clause for that
> > argument.
> >
> > Having added Result.set_feature_clause to the relevant 8 routines of
> > ET_AST_FACTORY, I am now getting features processed.
>
> You should not do that, but use ET_DECORATED_AST_FACTORY instead.
> This is what is done in $GOBO/test/tools and in
> $GOBO/example/tools/bang2create.

-- 
Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein