Re: eiffel parser in SmartEiffel

On 22 Jul., 11:57, lee <cogn...@[EMAIL PROTECTED]
> wrote:

> I will have to look at the post because I did not see it.  It would

It was about the EiffelDoc or how they call it. It has nothing to do
with the runtime speed of compiled apps.

> I'm not so sure.  Linux is improving a great deal.  Now, this might
> not help your specific market, but it could.

Yes, Linux is a very special market. Might be easier with AIX/Solaris/
HP-UX
but they don't have any market share anymore.

> I understood most of this paragraph except for the last sentence.


> Could you not have learned eiffel and then coded your software in
another
> language using the concepts you learned from eiffel?

At least the the Eiffel methodology is a huge helper and some of your
experience assets that you can rescue to other languages/systems when
you
decide not to use Eiffel anymore.

> Or are you saying
> that you could not have bug free software unless you use eiffel?
> Answering yes to the second sentence is a powerful advertisement for the
eiffel
> language.

Yes, but i'm not sure if this is marketing for Eiffel or bad marketing
for my chaotic
development style, my tight time schedules and my lack of money. I can
only say that the
ability to get the SmallEiffel stack traces from customers (i had to
make a lot of patches
to the exception handling to get this right) was the hugest benefit of
all and it pays back for all the other problems i had from Eiffel.
Sure a lot of it depends on the
DBC in the runtime libraries and that errors are re****ted
immediately.

If somebody would embedd gdb into the product and delivered it with
your main app and make it possible to send full stacktraces to me, i'm
sure that would helped me in other languages.  But i don't know of
anybody offering such a solution.

And i've never seen a C/C++ or whatever library with enough asserts
that would do what Eiffel is doing for me.

So yes, i find Eiffel still great, thats why i'm reading this
newsgroup and still using it. I like it so much that from time to time
i'm thinking about producing my own ECMA Eiffel compiler (i certainly
would do it if SmallEiffel had a BSD License). But then the real
worlds comes in and remembers me to make money to pay my bills on each
first of a month.

I like writing compilers and i have a lot of ideas what could be done.
Maybe if a new generation of CPU with fine grained multithreading
comes
it is a chance because for this everything needs to be rewritten.

> apologist for the SmartEiffel team, but since that time they have
> seemed to become more open in their development style with SVN access
> to their code.  The number of libraries has increased, etc.  Still, it

Read only. Don't forget this. And - yes, its ba****ng - between 2003
and 2005
every single decision they made was IMHO wrong. There aren't many
software
projects where i can say this.

> But, people have the freedom to fork the project if they wish.

Thats what i did. But it is not good for the community (well there is
no
community anymore).

> Again, the large clients I see are always struggling. It seems that
> they
> spend a lot of time with Java evaluating different frameworks.

Frameworks are different then libraries. First you need the libraries
and even this is something not yet available. Don't take my words for
EiffelStudio - i'm commenting on SmallEiffel, but i heared that
EiffelStudio
still has the problems. Look at Python and then look back into Eiffel
world.