Re: Turning off CATCALL detection with gec

I think that this command-line option is independent
of the type of Eiffel config file passed as input.

But I'm not sure I understand the problem. Are you
saying that gec reports the CAT-call error at compilation
time despite the fact that you use the command-line option
--catcall=no? Note that if you use --catcall=no at
compilation time, the error will nevertheless be reported
at run-time.

-- 
Eric Bezault
mailto:[email protected]
http://www.gobosoft.com


On 12/18/2010 11:04 AM, Colin Paul Adams wrote:
> According to the gec command-line help, there is an option
> --catcall=no|error|warning with the default being warning.
>
> Does this only apply to ace input, rather than xace? I seem to get
> errors that ISE 6.7 passes (incorrectly), and results in a call-on-void
> target at runtime.
>
> The (correct) error I get from gec is:
>
> [VUAR-2] class COW (HERBIVORE,40,5): the 1-th actual argument (of type 'PLANT')
> does not conform to the corresponding formal argument (of type 'GRASS')
> of feature `eat'.
>
> This is using a test based on the incomplete example in the LCON section of the
> Eiffel FAQ.
>
> Are there some categories of CATCALL that gec always reports, regardless
> of the setting?




------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d