CONSTRUCT undefines clone_node and new_tree?

[Joachim Baran]

Hello,

I am trying to build a parser and as one of the first steps towards
implementing it I tried to follow the example in the online
documentation. So, right now, I created one class that inherits from
AGGREGATE and I provided implementations for the deferred features
production and construct_name.

Unfortunately, it seems that AGGREGATE's parent class CONSTRUCT
undefines clone_node and new_tree, which are defined in CONSTRUCT's
parent class TWO_WAY_TREE. When I try to build my program, I get the
error message that my parser class should be declared deferred,
because those two features are missing in it. The parser documentation
does not mention these features, so I assume I am doing something
wrong? I am using EiffelStudio 6.4.7.9451 on OS X.

Thanks,
Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

[Joachim Baran]

Hello, again!

2009/11/7 Joachim Baran <[hidden email]>:
> Unfortunately, it seems that AGGREGATE's parent class CONSTRUCT
> undefines clone_node and new_tree, which are defined in CONSTRUCT's
> parent class TWO_WAY_TREE. When I try to build my program, I get the
> error message that my parser class should be declared deferred,
> because those two features are missing in it.
The problem has magically disappeared now.

All I did was to copy my project files to a Linux system, which
involves me deleting the EIFGENs folder, where everything seemed to
work fine. Just out of curiosity I copied the files back to my OS X
system and now I do not get an error anymore.

Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

[Joachim Baran]

Hello, yet again!

I am getting again errors that TWO_WAY_TREE has deferred features
clone_node and new_tree. When I double-click on the error message it
becomes clear that these features are defined though.

I said beforehand that deleting the EIFGENs folder seemed to help.
Well, it does not work anymore. I have tried multiple combinations of
deleting the EIFGENs folder and recompiling, with and without
restarting EiffelStudio, but everything I try seems futile. This time,
I am using EiffelStudio 6.4.7.9451 linux-x86.

Is there a solution to this problem?

Thanks,
Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

[Jimmy Johnson]

Joachim, I'm sorry I can't fix your problem but I couldn' help but noitice that you asked the question, answered it, and argued with yourself before anyone replied. ;)  Perhaps I can look at this later.

jjj



--- In [hidden email], Joachim Baran <joachim.baran@...> wrote:

>
> Hello, yet again!
>
> I am getting again errors that TWO_WAY_TREE has deferred features
> clone_node and new_tree. When I double-click on the error message it
> becomes clear that these features are defined though.
>
> I said beforehand that deleting the EIFGENs folder seemed to help.
> Well, it does not work anymore. I have tried multiple combinations of
> deleting the EIFGENs folder and recompiling, with and without
> restarting EiffelStudio, but everything I try seems futile. This time,
> I am using EiffelStudio 6.4.7.9451 linux-x86.
>
> Is there a solution to this problem?
>
> Thanks,
> Joachim
>
> --
> B.1079 Michael Smith Building
> Faculty of Life Sciences
> The University of Manchester
> Oxford Road
> Manchester
> M13 9PT
> United Kingdom
>

[Joachim Baran]

Hello!

2009/11/13 Jimmy Johnson <[hidden email]>
> Joachim, I'm sorry I can't fix your problem but I couldn' help but noitice that you asked the question, answered it, and argued with yourself before anyone replied. ;) Perhaps I can look at this later.
Well, I like arguing with myself. :)

In the meantime, I had a look at the source code of the EiffelParse
example that comes with EiffelStudio 6.4. It turns out that both
features are implemented, but their visibility is restricted to
TWO_WAY_TREE only. Classes deriving from AGGREGATE and the like are
actually re-implementing the feature. In other words, I solved the
problem I had myself now.

However, there are some other quirky constraints on how to parse a
document, which are easy to figure out when the corresponding
pre-/post-conditions are violated, but I would have liked to read
about that in the documentation. In fact, besides the tutorial, there
does not seem to be much to read about EiffelParse at all. Are there
any plans to update or extend the documentation about EiffelParse and
EiffelLex?

BW,
Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

[Emmanuel Stapf]

> However, there are some other quirky constraints on how to parse a
> document, which are easy to figure out when the corresponding
> pre-/post-conditions are violated, but I would have liked to read
> about that in the documentation. In fact, besides the tutorial, there
> does not seem to be much to read about EiffelParse at all. Are there
> any plans to update or extend the documentation about EiffelParse and
> EiffelLex?

Have you looked at http://docs.eiffel.com/book/solutions/text-processing ?

Manu

[Joachim Baran]

2009/11/13 Emmanuel Stapf [ES] <[hidden email]>
> Have you looked at http://docs.eiffel.com/book/solutions/text-processing ?
Yes, those are the tutorials I was looking at. They are good, but I
think there is more to Eiffel's lexer/parser generation than it is
described in there. Anyway, I finally managed to do what I wanted to
do, but I only wish there would have been an easier way to get round
to it in retrospective.

Thanks,
Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom