> Bert Verhees wrote:
>>
>> In so far, not because I like to disagree, but regrettable, many of the
>> function/method-bodies in the Eiffel-code are empty. Eiffel seems merely
>> to be/have been used as a kind of case-tool instead of really building
>> a openehr kernel-implementation.
>> Which is a good use for Eiffel, but it is something else then writing an
>> implementation
>
>
> I don't know what you're referring to, Bert. The Eiffel code has most
> definitely been written as an implementation. We are using it. ADL
> Workbench
> is built entirely in Eiffel. The Ocean Archetype Editor, which is written
> in
> VB.NET, uses the Eiffel kernel classes in the form of a .NET assembly.
>
> Maybe you've been looking at the Eiffel code via EiffelStudio's "contract"
> or "interface" views: these views hide the implementation of the classes.
>
> - Peter

Sad is that I cannot get the EiffelStudio (Linux-version) to run on my
Linux-machine, some vague errors and nothing to find on the Internet.
The ADLworkbench has another problem, in Wine, it does not refresh the
treeviews (after clicking on it). Too bad, both things, so I don't use
them both, which I regret. But I hate working on Windows. There are other
advantages on my Linux-environment which I enjoy very much.
-----------------
So I was looking at the website, I did (also in the past) take a look in
the SVN TRUNK tree, because I wanted to check something, I use it as a
case tool, so for me it is no problem. Yesterday I looked at three files,
all had empty function bodies (f.e. ) in composition.e which is a rather
crucial file.

Take a look yourself:
http://svn.openehr.org/ref_impl_eiffel/TRUNK/libraries/openehr/src/rm/composition/composition.e

Did I miss something and is there a code-tree which has the function
bodies? Please tell me.
I must have looked at the wrong place, excuse me for my mistake.

I survived ;-)

kind regards
Bert


>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>



Reply via email to