Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Java Checked Exceptions Date: Sun, 7 Feb 2016 21:55:50 +0100 Lines: 19 Message-ID: References: <56b601cc$0$23722$e4fe514c@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 6WiOwWms1sA2UBgn0EF9mgB9pm/zeYMyRJISQNb5ZcSqloUSE= Cancel-Lock: sha1:0tiEGlud5dhPd+3dtNKUccHufLE= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:33645 On 07.02.2016 15:09, Stefan Ram wrote: > Some methods can't know all their exceptions at > documentation time because they call other methods that > are only determined at runtime. But this is also the case > where checked exceptions are difficult to use. How should that be possible? Can you show an example where not all checked exceptions can be determined at documentation time (i.e. after successful compiling)? Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/