Re: gelex "bug"?

Eric Bezault <ericb-D6Qt/9opevxWk0Htik3J/[email protected]>
Newsgroups gmane.comp.lang.eiffel.gobo.general
Organization Gobo
Message-ID <[email protected]>
Hi Katrin,

Katrin Bretscher wrote:
> i am trying to use gelex and proceeded as described on the gobosoft 
> page. however, when i try to add $GOBO/library/kernel/spec/se to my .ace 
> file, i get a compile error:
> ----
> Error code: VD24
> Lace error: cluster contains conflicting declaration for basic class.
> What to do: choose the appropriate version of the class; exclude
>   the other from system (by moving it to another directory, or
>   by using the Lace Exclude clause, see ETL D.9, p. 524);
>   or if class is needed change its name it to remove the conflict.
> 
> 
> Class name: SPECIAL
> First cluster: se
> Second cluster: base.kernel.classic
> ----
> 
> i don't think i can exclude either of these classes, neither do i want 
> to rename the kernel or library class... is this a known problem - and 
> if so, could you point me to the solution? unfortunately, i haven't been 
> able to find any other info on the matter :-/

The spec directory contains one subdirectory for each
supported Eiffel compiler (ise for ISE Eiffel, se for
SmartEiffel, ve for Visual Eiffel). Only one of these
subdirectories should be included in your Ace file. It
looks like you are using ISE Eiffel, so you should keep
$GOBO/library/kernel/spec/ise and exclude the other
subdirectories.

-- 
Eric Bezault
mailto:ericb-D6Qt/9opevxWk0Htik3J/[email protected]
http://www.gobosoft.com



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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.