Re: What is the exact problem with SE and GOBO ?

Colin Paul Adams napisał(a):

>>>>>>"Damian" == Damian Dobroczyñski <damian-UNDDejp0Q2SrDJvtcaxF/[email protected]> writes:
>>>>>>            
>>>>>>
>
>    Damian> Hi all.  I would like to use GOBO package with SE 2.2. I
>    Damian> need to know all kind of problems SE 2.2 has with GOBO
>    Damian> (besides this legendary "upper/lowercase" problem)? Maybe
>    Damian> strange inheritance? ANY is not ANY? Did somebody
>    Damian> investigate this problem deeply?
>
>    Damian> Thnx for quick and exact answer.
>
>Coming up:
>
>Gobo is an Eiffel library.
>SE 2.2 (beta 3 onwards) is a compiler for an Eiffel-like language, but
>not Eiffel.
>
>The case problem is the biggest one - it is overwhelming because
>attributes with names such as STRING_ (used very extensively
>throughout the Gobo libraries) are syntax errors in the language
>supported by SE 2.2.
>
>  
>
Well, I've written a Python script that tried to transform *all* of the 
upper case identifier to lower case (for features only of course). Of 
course, it will not work for many cases like constant identifiers used 
in parse and lexer clusters but ... after 2 hours I've managed to 
compile the simplest program using ET_EIFFEL_PARSER. So, the main proble 
is the case problem.
I've also found a problem with multiple feature definition in the 
inheritance tree but it's easy to fix. I've found "deferred class" 
problem while compiling with ISE Eiffel 5.6 but this is described in my 
second post. I've also found non-consistent feature names for the same 
feature (written in mixed upper/lower case in different places). I've 
also experienced VE failure with GEANT compilation. As you see it is not 
so simple to be sticked to Eiffel.

When developing a software I find it very reasonable to try to find 
*common* *denominator* for the broadest set of compilers I know. That 
what I've done when working with C++ language. This "case" problem I've 
found in Eiffel community is radiculus to me. The solution is simple. 
Find the *common* *denominator* for all compilers. The number of them 
(compilers) is 3 (three). Not too many. As a fact, there are only three 
C++ compilers mainly used by programmers: VC, GCC and Watcom. You see: 
3.  Of course, there are a lot of them on the market and believe me: 
It's a big pain to write portable software. But people do this inspite 
of many problems with compilers. Nobody offended.

Back to Eiffel: if "STRING_" is compiled by two of them but the last one 
failed then use "string_" which will be perfectly compiled by all of the 
compilers. Am I right? That is the best solution for the community if 
one of the compilers vendors refuses to make the compiler conformant 
with our dreams and standards. It happens. It happens all of the time...

>Stick to Eiffel.
>  
>
I would like to.

B.regards.

Damian



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page
http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/saFolB/TM
--------------------------------------------------------------------~-> 

To Post a message, send it to:   [email protected]
To Unsubscribe, send a blank message to: [email protected] 
Yahoo! Groups Links

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

<*> To unsubscribe from this group, send an email to:
    [email protected]

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