[m-dev.] checked exceptions.
Matt Giuca
matt.giuca at gmail.com
Wed Feb 13 11:19:13 AEDT 2013
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.
On 13 Feb 2013 10:52, "David Overton" <david at overtons.id.au> wrote:
> On 13 February 2013 10:32, Paul Bone <paul at bone.id.au> 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
> developers at lists.mercurylang.org
> http://lists.mercurylang.org/listinfo/developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/developers/attachments/20130213/830317cf/attachment.html>
More information about the developers
mailing list