In message <Vv6dnU-ApMDb_kzQnZ2dnUVZ_tWdnZ2d@web-ster.com>, Tim Wescott
<tim@seemywebsite.com> writes
>On 05/16/2011 12:16 AM, Chris H wrote:
>> In message<j9SdnZniV9-rUU3QnZ2dnUVZ_qidnZ2d@giganews.com>, vikasvds
>> <vikasetc@n_o_s_p_a_m.gmail.com> writes
>>> Hi,
>>>
>>> I am just curious to know what the reason behind MISRA rule 111.
>>
>> You are asking in the wrong place.
>>
>> Try the forum at
>>
>> http://www.misra-c.org.uk
>>
>>> Could somebody please put light on this.
>>
>> No one in this NG can.
>>
>Better yet, try reading the multitude of responses to your post on the
>12th. Jeesh.
I know... proved my point
--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Reply by Tim Wescott●May 16, 20112011-05-16
On 05/16/2011 12:16 AM, Chris H wrote:
> In message<j9SdnZniV9-rUU3QnZ2dnUVZ_qidnZ2d@giganews.com>, vikasvds
> <vikasetc@n_o_s_p_a_m.gmail.com> writes
>> Hi,
>>
>> I am just curious to know what the reason behind MISRA rule 111.
>
> You are asking in the wrong place.
>
> Try the forum at
>
> http://www.misra-c.org.uk
>
>> Could somebody please put light on this.
>
> No one in this NG can.
>
Better yet, try reading the multitude of responses to your post on the
12th. Jeesh.
--
Tim Wescott
Wescott Design Services
http://www.wescottdesign.com
Do you need to implement control loops in software?
"Applied Control Theory for Embedded Systems" was written for you.
See details at http://www.wescottdesign.com/actfes/actfes.html
Reply by Chris H●May 16, 20112011-05-16
In message <j9SdnZniV9-rUU3QnZ2dnUVZ_qidnZ2d@giganews.com>, vikasvds
<vikasetc@n_o_s_p_a_m.gmail.com> writes
>Hi,
>
>I am just curious to know what the reason behind MISRA rule 111.
No one in this NG can.
--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Reply by vikasvds●May 16, 20112011-05-16
Hi,
I am just curious to know what the reason behind MISRA rule 111.
The rule says - Bit fields shall only be defined to be one of type unsigned
int or signed int
I have used UINT32 instead of unsigned int in my code but compiler has
thrown a warning says - "field type should be int"
Could somebody please put light on this.
Thanks
Vikas
---------------------------------------
Posted through http://www.EmbeddedRelated.com