It seems like an idea that fits well with Mercury's existing philosophy. But won't this make all existing code break? It would have to be turned off by default and enabled with a compiler flag, surely. <div class="gmail_quote">On 13 Feb 2013 10:52, "David Overton" <<a href="mailto:david@overtons.id.au">david@overtons.id.au</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 13 February 2013 10:32, Paul Bone <<a href="mailto:paul@bone.id.au">paul@bone.id.au</a>> wrote: > If your method might throw a checked exception then it must declare the > possibility of the exception as part of it's signature. Any method calling > this method is forced either to catch and handle the exception, or to > declare that it may be thrown. How would this work with higher-order code? _______________________________________________ developers mailing list <a href="mailto:developers@lists.mercurylang.org">developers@lists.mercurylang.org</a> <a href="http://lists.mercurylang.org/listinfo/developers" target="_blank">http://lists.mercurylang.org/listinfo/developers</a> </blockquote></div>