Re: The result of 1 << 32

On 29 Oct 2005 23:23:24 GMT, in comp.lang.c , richard@xxxxxxxxxxxxxxx
(Richard Tobin) wrote:

>In article <q6q7m1t3sh4kcf2sk7q8ffmvjkvbc8fai6@xxxxxxx>,
>Mark McIntyre <markmcintyre@xxxxxxxxxxx> wrote:
>
>>This ensures your audience learn /first/ that its UB and naughty,
>>/then/ about how it might be handled.
>
>Explaining the plausible implementations often (as in this case)
>explains why the behaviour is undefined. Understanding that is better
>than just knowing that it's undefined.

.... and if you actually read what I say, you'll see that I am still
advocating supplying both bits of information, as you suggest.

My point was that if you stress first that its UB, then explain likely
implementation-specific solutions, you ensure that newbies leave
knowing they can't rely on it.

I've noticed that undergrad level newbies will read para 1 then doze
off or start to play with their mobe, and so miss the rest of the
Lesson...
--
Mark McIntyre
CLC FAQ <http://www.eskimo.com/~scs/C-faq/top.html>
CLC readme: <http://www.ungerhu.com/jxh/clc.welcome.txt>

----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
.