> > A compiler writer can't do with just a
> > bunch of words, he needs a clear choice.
> 
> Exactly, and IMHO the only choice he should make is to do NOTHING
> special.

You can't sneak out of this. Assuming the main() is at the end of the
code and does not end with a return (both are normal practice) doing
nothing has the same effect as jumping to 0. So like it or not, that is
the effect you are choosing.

Or when the compiler happens to arrange the code in a different way,
your choice is to jump into the function that happens to be after the
main(). Which could be a different function, depending on the version of
the compiler (if you are lucky) or on the phase of the moon and/or
things involving dead fish (if you are less lucky).

IMHO both 'goto $' and 'goto 0' are better choices. I prefer 'goto $',
but 'goto 0' is still much better than completely undefined behaviour.
Which isn't even allowd by the C standard. Luckily I wrote the Jal
'standard' myself so I could make the 'goto $' part of the definition :)
(mental note: did I?)

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist