The Eiffel Compiler

45 Messages Forum Options Options
Permalink
1 2 3
Helmut Brandl
The Eiffel Compiler
Reply Threaded More
Print post
Permalink
The Eiffel Compiler tecomp 0.2 has been released.

It is a small command line compiler and executes Eiffel programs in a
virtual machine. A considerable subset of the Eiffel language is already
accepted by the compiler. However, it is still a beta version.

Download: http://www.sourceforge.net/projects/tecomp (for unix and
windows systems)
Documentation: http://tecomp.sourceforge.net

Regards
Helmut

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Eric Bezault
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
Helmut Brandl wrote:
> The Eiffel Compiler tecomp 0.2 has been released.
>
> It is a small command line compiler and executes Eiffel programs in a
> virtual machine. A considerable subset of the Eiffel language is already
> accepted by the compiler. However, it is still a beta version.

Why didn't you use Eiffel to implement it?

Any chance that you use FreeELKS as kernel library? I think that
for a compiler to be successful, it should be able to compile
programs written for other compilers. And my experience shows that
this is impossible to achieve without being source code compatible
at the kernel library level (interface compatibility as was suggested
by ELKS'95 is not enough). That's why the Gobo compiler uses FreeELKS.
Surely FreeELKS still uses Eiffel constructs that are not in ECMA
Eiffel anymore. But that's the price to pay in order to let all
existing Eiffel users smoothly convert their code to the new standard.

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

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Peter Häfliger
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
Dear all
 
I am not a frequent Eiffel user and just an occasional reader of this list, so please forgive my ignorance, but:
 
What do we need yet another Eiffel compiler anyway?
 
Wouldn't the effort needed to implement it not be better spent in improving existing compilers/environments?
 
Sincerely yours,
 
Peter

--- Eric Bezault <ericb@...> schrieb am Sa, 12.7.2008:

Von: Eric Bezault <ericb@...>
Betreff: Re: [eiffel_software] The Eiffel Compiler
An: eiffel_software@...
Datum: Samstag, 12. Juli 2008, 2:33






Helmut Brandl wrote:
> The Eiffel Compiler tecomp 0.2 has been released.
>
> It is a small command line compiler and executes Eiffel programs in a
> virtual machine. A considerable subset of the Eiffel language is already
> accepted by the compiler. However, it is still a beta version.

Why didn't you use Eiffel to implement it?

Any chance that you use FreeELKS as kernel library? I think that
for a compiler to be successful, it should be able to compile
programs written for other compilers. And my experience shows that
this is impossible to achieve without being source code compatible
at the kernel library level (interface compatibility as was suggested
by ELKS'95 is not enough). That's why the Gobo compiler uses FreeELKS.
Surely FreeELKS still uses Eiffel constructs that are not in ECMA
Eiffel anymore. But that's the price to pay in order to let all
existing Eiffel users smoothly convert their code to the new standard.

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














      __________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com

[Non-text portions of this message have been removed]


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Bertrand Meyer
Research positions at the Chair of Software Engineering at ETH
Reply Threaded More
Print post
Permalink
There are some openings at the Chair of Software Engineering for
postdocs or PhDs with a strong theoretical and practical background (in
particular in formal methods). Experience in Eiffel is particularly
appreciated. For details please see http://se.ethz.ch/jobs/index.html.

-- Bertrand Meyer


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Helmut Brandl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
In reply to this post by Eric Bezault

> Any chance that you use FreeELKS as kernel library? I think that
> for a compiler to be successful, it should be able to compile
> programs written for other compilers. And my experience shows that
> this is impossible to achieve without being source code compatible
> at the kernel library level (interface compatibility as was suggested
> by ELKS'95 is not enough). That's why the Gobo compiler uses FreeELKS.
> Surely FreeELKS still uses Eiffel constructs that are not in ECMA
> Eiffel anymore. But that's the price to pay in order to let all
> existing Eiffel users smoothly convert their code to the new standard.
>
>  
Hello Eric,

I would like to use FreeELKS. But FreeELKS contains much more than the
kernel library and is based on the ISE runtime. Therefore it is
difficult to use it as a "standard". But if I look only on the contents
of "kernel" it is possible to use large portions of it. I will try to be
compatible as much as possible.

However I am convinced that Eiffel needs a good specification of the
kernel library and an operating system interface library. If I read the
book of Kernighan and Ritchie "The C programming language" I find a very
clear, concise and nearly minimal definition of the "standard" libraries
one needs to do most of the programming tasks. It relates to I/O,
operating system interface like raw file handling, time and date etc. I
wish the Eiffel community had a similar definition.

It is a pity to have such a nice, clean, elegant and powerful language
as Eiffel but not to have a standard set of libraries for it .... :-(

Regards
Helmut

http://www.sourceforge.net/projects/tecomp
http://tecomp.sourceforge.net

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Eric Bezault
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
Helmut Brandl wrote:

>> Any chance that you use FreeELKS as kernel library? I think that
>> for a compiler to be successful, it should be able to compile
>> programs written for other compilers. And my experience shows that
>> this is impossible to achieve without being source code compatible
>> at the kernel library level (interface compatibility as was suggested
>> by ELKS'95 is not enough). That's why the Gobo compiler uses FreeELKS.
>> Surely FreeELKS still uses Eiffel constructs that are not in ECMA
>> Eiffel anymore. But that's the price to pay in order to let all
>> existing Eiffel users smoothly convert their code to the new standard.
>>
>>  
> Hello Eric,
>
> I would like to use FreeELKS. But FreeELKS contains much more than the
> kernel library and is based on the ISE runtime. Therefore it is
> difficult to use it as a "standard". But if I look only on the contents
> of "kernel" it is possible to use large portions of it. I will try to be
> compatible as much as possible.
>
> However I am convinced that Eiffel needs a good specification of the
> kernel library and an operating system interface library. If I read the
> book of Kernighan and Ritchie "The C programming language" I find a very
> clear, concise and nearly minimal definition of the "standard" libraries
> one needs to do most of the programming tasks. It relates to I/O,
> operating system interface like raw file handling, time and date etc. I
> wish the Eiffel community had a similar definition.
>
> It is a pity to have such a nice, clean, elegant and powerful language
> as Eiffel but not to have a standard set of libraries for it .... :-(

As I said in my previous message, having a kernel library standard
at the interface level as was done by ELKS'95 proved to be not
enough to guarantee interoperability between Eiffel compilers.
To have true interoperability we need to have a least a kernel
library standard at the implementation level. That's what FreeELKS
tries to achieve. Of course it is based on ISE's library. But
since gec and tecomp don't have a user community yet I'm now
convinced that it is better to preserve the ISE's user community
and be compatible with it. I see no advantage in having a micro
gec Eiffel community or a micro tecomp Eiffel community. We need
Eiffel compilers that are able to compile programs written with
other Eiffel compilers. Having a standard set of Eiffel libraries
would be great, but we never managed to achieve that after 20
years. With FreeELKS there is a real opportunity to achieve
interoperability. gec and EiffelStudio are almost fully
interoperatable thanks to that. So in a way you could consider
FreeELKS as a de facto standard.

I'm still puzzled as to why you didn't use Eiffel to implement
your compiler.

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

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Eric Bezault
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
In reply to this post by Peter Häfliger
Peter Häfliger wrote:
> I am not a frequent Eiffel user and just an occasional reader of this list, so please forgive my ignorance, but:
>  
> What do we need yet another Eiffel compiler anyway?
>  
> Wouldn't the effort needed to implement it not be better spent in improving existing compilers/environments?

Or yet even better: implement missing Eiffel libraries.

That being said, I'm not too much concerned about the
"yet another Eiffel complier". Having different Eiffel compilers
may be interesting if they provide different compilation techniques
that may have their own interest but cannot be integrated in
a straightforward way in existing compilers. What I'm more
concerned about is if we get "yet another incompatible Eiffel
compiler". That's why gec's primarily goal is to provide
interoperability with EiffelStudio, being ECMA compliant
being only a consequence of that since ISE is pursuing
that target.

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

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Helmut Brandl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
In reply to this post by Eric Bezault

> As I said in my previous message, having a kernel library standard
> at the interface level as was done by ELKS'95 proved to be not
> enough to guarantee interoperability between Eiffel compilers.
> To have true interoperability we need to have a least a kernel
> library standard at the implementation level. That's what FreeELKS
> tries to achieve. Of course it is based on ISE's library. But
> since gec and tecomp don't have a user community yet I'm now
> convinced that it is better to preserve the ISE's user community
> and be compatible with it. I see no advantage in having a micro
> gec Eiffel community or a micro tecomp Eiffel community.
I fully agree. The Eiffel community is not very big and we should not do
anything to split this small community. Therefore for tecomp I decided
(as opposed to SmartEiffel) to implement standard Eiffel. I will take
your remark concerning FreeELKS serious and see that tecomp can accept
FreeELKS. Accepting FreeELKS would imply to be able to compile programs
written based on FreeELKS. I consider this as a challenge and an
opportunity.

Having different tools and compilers for a Eiffel should help to spread
the use of Eiffel. Each compiler wil have different strengths and
weaknesses. Since tecomp startet with compiling for execution in its
virtual machine it is really very, very simple to write small Eiffel
programs. You just write a few lines of hello_world.e and
hello_world.ace and execute it. Without any need to do C compilation,
having a huge EIFGEN and soon. So this could attract perl, tcl or users
of other scripting languages which want to implement in a clean object
oriented language. Or for example users of EiffelStudio which want the
possiblity to write small programs to try something without all the
overhead of a complete project.

For writing Eiffel applications of significant size using standard
Eiffel at this point in time EiffelStudio is clearly the method of choice.
> I'm still puzzled as to why you didn't use Eiffel to implement
> your compiler.
>
>  
At the beginning I tried to do this. I wanted to use SmartEiffel with
Gobos Lex and Yacc implementation. But due to the policy of SmartEiffel
to implement their own dialect of Eiffel I decided not to do this.

Then I tried EiffelStudio. But I was shocked by the 500 MByte installed
size and by the size of a tiny project like "Hello world". Then you will
encounter some problems in distributing your compiler. Either you
require that your users will have an installation of EiffelStudio or you
distribute the binary (i.e. distribute different binaries for each
machine type and operating system ...) or you distribute the compiled to
c version of your compiler together with the source code. All a little
bit complicated if you want to attract new users. There is the
possibility that they say "Eiffel might be nice in theory, but too
complicated to make it run".

Since nearly all Unix installations have a good C/C++ compiler it is
convenient to use it and provide only compiled binaries for Windows.
Sometimes one have to accept facts. C/C++ is a defacto standard on a
machine used for SW development (if think for this reason SmartEiffel,
EiffelStudio and gec decided to compile to C and not Pascal, Fortran, ....).

Having some simple macros enable you to use Design by Contract in C++
(clearly not the full power of DbC, but it is not as bad).



Regards
Helmut

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Eric Bezault
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
Helmut Brandl wrote:

> Then I tried EiffelStudio. But I was shocked by the 500 MByte installed
> size and by the size of a tiny project like "Hello world". Then you will
> encounter some problems in distributing your compiler. Either you
> require that your users will have an installation of EiffelStudio or you
> distribute the binary (i.e. distribute different binaries for each
> machine type and operating system ...) or you distribute the compiled to
> c version of your compiler together with the source code. All a little
> bit complicated if you want to attract new users. There is the
> possibility that they say "Eiffel might be nice in theory, but too
> complicated to make it run".

Or new users may think that Eiffel is not a so good programming
language after all since you didn't choose to use it to write
your compiler.

> Since nearly all Unix installations have a good C/C++ compiler it is
> convenient to use it and provide only compiled binaries for Windows.
> Sometimes one have to accept facts. C/C++ is a defacto standard on a
> machine used for SW development (if think for this reason SmartEiffel,
> EiffelStudio and gec decided to compile to C and not Pascal, Fortran, ....).

The Eiffel compilers that you mentioned use C as an
high-level portable assembly language, not as a development
programming language.

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

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Helmut Brandl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
Eric Bezault wrote:

> Helmut Brandl wrote:
>  
>> Then I tried EiffelStudio. But I was shocked by the 500 MByte installed
>> size and by the size of a tiny project like "Hello world". Then you will
>> encounter some problems in distributing your compiler. Either you
>> require that your users will have an installation of EiffelStudio or you
>> distribute the binary (i.e. distribute different binaries for each
>> machine type and operating system ...) or you distribute the compiled to
>> c version of your compiler together with the source code. All a little
>> bit complicated if you want to attract new users. There is the
>> possibility that they say "Eiffel might be nice in theory, but too
>> complicated to make it run".
>>    
>
> Or new users may think that Eiffel is not a so good programming
> language after all since you didn't choose to use it to write
> your compiler.
>  
This might be possible. I considered that argument as well. But the
other reasons I gave pushed me into the other direction. I think the
only solution is to spread Eiffel such that it is standard to have a
(hopefully standard compliant) Eiffel compiler on development machines.
Once that is reached you can distribute source packages for programs
written in Eiffel as it is done currently for C/C++/Java/TCL/PERL.
Unfortunatly, this is not yet the case. So if you want to distribute a
source package for an Eiffel program you have to include also an Eiffel
compiler or the compiled binaries of your program. At least if you want
acceptance from users which do not yet have an installed Eiffel compiler.

But lets concentrate on our common goal to spread the use of Eiffel.

Helmut Brandl
http://www.sourceforge.net/projects/tecomp
http://tecomp.sourceforge.net


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Bertrand Meyer
RE: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
General observations:

1.  If the goal is to write “Hello World” there is no absolute need for
Eiffel.

2. The footprint of a small application with EiffelStudio can be reduced
if necessary (that hasn’t been a major request from users so far,
although it is true that people who play with the environment complain
about this at the beginning). This would be an easier effort, by a
couple of orders of magnitude maybe, than writing a new compiler.

3.  > But lets concentrate on our common goal to spread the use of
Eiffel.
Very nice. Then producing a new compiler is probably around number 216
on the list of helpful initiatives. Number 1 (and 2, and 3 and more) is
to produce libraries. What Eiffel needs at this point is reusable
components of high quality, hundreds of them, complementing the existing
libraries (EiffelBase, EiffelNet, EiffelVision, the Gobo libraries
etc.). If you really want to help , this is what you should be doing. It
has the advantage of being tractable: a single person can achieve effect
and visibility in a matter of months or even weeks, as opposed to the
person-decades that a compiler effort requires before producing anything
usable. Also, it will give you experience of programming in Eiffel.
Besides, it's fun. You might even come to appreciate EiffelStudio (once
you get past Hello World) and remedy its limitations by contributing to
it (http://dev.eiffel.com).

4. This mailing list is for users of EiffelStudio to help each other
when encountering technical issues. Other discussions, however
interesting, should be conducted in one of the many other available
forums.

Thanks,

-- BM


From: eiffel_software@...
[mailto:eiffel_software@...] On Behalf Of Helmut Brandl
Sent: Sunday, 13 July, 2008 19:37
To: eiffel_software@...
Subject: Re: [eiffel_software] The Eiffel Compiler

Eric Bezault wrote:
> Helmut Brandl wrote:
>
>> Then I tried EiffelStudio. But I was shocked by the 500 MByte
installed
>> size and by the size of a tiny project like "Hello world". Then you
will
>> encounter some problems in distributing your compiler. Either you
>> require that your users will have an installation of EiffelStudio or
you
>> distribute the binary (i.e. distribute different binaries for each
>> machine type and operating system ...) or you distribute the compiled
to
>> c version of your compiler together with the source code. All a
little
>> bit complicated if you want to attract new users. There is the
>> possibility that they say "Eiffel might be nice in theory, but too
>> complicated to make it run".
>>
>
> Or new users may think that Eiffel is not a so good programming
> language after all since you didn't choose to use it to write
> your compiler.
>
This might be possible. I considered that argument as well. But the
other reasons I gave pushed me into the other direction. I think the
only solution is to spread Eiffel such that it is standard to have a
(hopefully standard compliant) Eiffel compiler on development machines.
Once that is reached you can distribute source packages for programs
written in Eiffel as it is done currently for C/C++/Java/TCL/PERL.
Unfortunatly, this is not yet the case. So if you want to distribute a
source package for an Eiffel program you have to include also an Eiffel
compiler or the compiled binaries of your program. At least if you want
acceptance from users which do not yet have an installed Eiffel
compiler.

But lets concentrate on our common goal to spread the use of Eiffel.

Helmut Brandl
http://www.sourceforge.net/projects/tecomp
http://tecomp.sourceforge.net
 


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Helmut Brandl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink

>  Other discussions, however
> interesting, should be conducted in one of the many other available
> forums.
>
> Thanks,
>
> -- BM
>
>  
Is there any forum to discuss issues of the next version of the ECMA
standard. As you already stated the mixing of catcall avoidance and
attached types has been an error in the ECMA standard of june 2006. But
in what direction is the ECMA commitee going? I agree, that a mailing
list for EiffelStudio is not the right place to discuss these matters
(although some listeners on this list have asked to continue the
discussion here), but I don't know any other forum to discuss issues
with the Eiffel standard. Could you give me some advice?

Thanks in advance

Helmut Brandl
http://www.sourceforge.net/projects/tecomp
http://tecomp.sourceforge.net

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Helmut Brandl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
In reply to this post by Eric Bezault
Eric Bezault wrote:
> Or yet even better: implement missing Eiffel libraries.
>
>  
Hello Eric,

which Eiffel libraries do you think are missing? If you give me some
indication maybe I can help.


Regards Helmut

http://www.sourceforge.net/projects/tecomp
http://tecomp.sourceforge.net



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Patrick Ruckstuhl
Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
For me, one of the libraries I miss most is

A simple, reliable, performant possibility to access a database, should
be easy to extend for different db systems without always going over
odbc or something similar

Regards,
Patrick



> Eric Bezault wrote:
>> Or yet even better: implement missing Eiffel libraries.
>>
>>  
> Hello Eric,
>
> which Eiffel libraries do you think are missing? If you give me some
> indication maybe I can help.
>
>
> Regards Helmut
>
> http://www.sourceforge.net/projects/tecomp
> http://tecomp.sourceforge.net
>
>
>
> ------------------------------------
>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto:eiffel_software-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
    eiffel_software-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Marco Piccioni
Re: Re: The Eiffel Compiler
Reply Threaded More
Print post
Permalink
To reiterate on what Patrick suggests, you could have a look at

http://dev.eiffel.com/Category:Persistence

http://dev.eiffel.com/Persistence_unified

for a possible start.

Also Hal Webre's learnlet on persistence can give you an idea of the
situation:

http://www.eiffel.com/developers/learning_maps/Training/Maps/PersistenceCanPayOff/index.html


Cheers

Marco


Patrick Ruckstuhl wrote:

>
>
> For me, one of the libraries I miss most is
>
> A simple, reliable, performant possibility to access a database, should
> be easy to extend for different db systems without always going over
> odbc or something similar
>
> Regards,
> Patrick
>
>  > Eric Bezault wrote:
>  >> Or yet even better: implement missing Eiffel libraries.
>  >>
>  >>
>  > Hello Eric,
>  >
>  > which Eiffel libraries do you think are missing? If you give me some
>  > indication maybe I can help.
>  >
>  >
>  > Regards Helmut
>  >
>  > http://www.sourceforge.net/projects/tecomp 
> <http://www.sourceforge.net/projects/tecomp>
>  > http://tecomp.sourceforge.net <http://tecomp.sourceforge.net>
>  >
>  >
>  >
>  > ------------------------------------
>  >
>
>


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/eiffel_software/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/eiffel_software/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:eiffel_software-digest@...
    mailto: