On 6/22/2011 16:31, clipka wrote:
> it's not even "implementation defined", nor is the behaviour
> explicitly "undefined" or "unspecified" if such limitations are exceeded.

It seems odd that a standard wouldn't describe what happens, even if only by 
describing it as "undefined what happens if you exceed a limit that the 
standard also doesn't specify." Because if you don't point out "hey, 
function calls may fail in undefined ways", then it would seem you're 
guaranteeing they'll obey the semantics the standard gives them.

> In a typical software production for embedded systems,

Sure, I understand how the things work. Thanks for the description. I just 
wondered what the standard had to say, if anything.  (But I don't wonder 
intensely enough to try to find it in the draft standards. :-)

-- 
Darren New, San Diego CA, USA (PST)
   "Coding without comments is like
    driving without turn signals."

Post a reply to this message