[Icc-mot] Strict Checkings to Strict?

[Edward Karpicz]

Any updates available? I was unable to reproduce compiler E! with your 
example.

Edward


----- Original Message ----- 
From: "Gene Norris" <genenorris at spotengineering.com>
To: <icc-mot at imagecraft.com>
Sent: Friday, April 06, 2007 19:03
Subject: [Icc-mot] Strict Checkings to Strict?


> Richard,
>
> When the strict checkings option is checked:
> Any deviation in type, when calling a function causes an _error_! I can 
> see why you would want a warning, but why do these cause errors?!
>
> For example:
> memset(mybuffer, 0, sizeof(mybuffer));
>
> Generates:
> type error in argument 1 to `memset';
> found `pointer to unsigned char' expected `pointer to void'
>
> Even modifiers like volatile cause an error...
>
> Shouldn't these be warnings?
>
> -- 
> Gene Norris
> Chief Engineer
>
> SPOT Engineering, Inc.
> 1261 Campground Road
> Lancaster, Ohio 43130
> 740.654.0880
> FAX.654.0889
>
> http://www.spotengineering.com/
>
> _______________________________________________
> Icc-mot mailing list
> Icc-mot at imagecraft.com
> http://dragonsgate.net/mailman/listinfo/icc-mot
>