Hello.
On Fri, 25 Dec 2015 10:31:43 +0100, Luc Maisonobe wrote:
Le 25/12/2015 04:46, Gilles a écrit :
On Thu, 24 Dec 2015 16:56:54 +0100, Luc Maisonobe wrote:
[...]
When our users build a large application, they rely on numerous
different libraries and tools, both open-source and proprietary.
Le 25/12/2015 04:46, Gilles a écrit :
> On Thu, 24 Dec 2015 16:56:54 +0100, Luc Maisonobe wrote:
[...]
When our users build a large application, they rely on numerous
different libraries and tools, both open-source and proprietary.
These libraries do have standard interface
On Thu, 24 Dec 2015 16:56:54 +0100, Luc Maisonobe wrote:
[...]
When our users build a large application, they rely on numerous
different libraries and tools, both open-source and proprietary.
These libraries do have standard interfaces so they can be used
together. The Java standard library is o
Hi Gilles,
It sounds like we're starting to coalesce on this. Hopefully this is not going
to come as too much of a shock :). [1] The exception patch will permeate
every class that throws an exception. We will have to delete all the other
exception and replace them with MathException. Here
Le 24/12/2015 14:13, Gilles a écrit :
> On Thu, 24 Dec 2015 09:36:34 +0100, Luc Maisonobe wrote:
>> Le 24/12/2015 01:41, Gilles a écrit :
>>> On Wed, 23 Dec 2015 20:18:10 +0100, Luc Maisonobe wrote:
Le 23/12/2015 14:32, Gilles a écrit :
> Hello.
>
> On Wed, 23 Dec 2015 10:38:03 +01
Hi Ole.
At this point in time, there are still incompatible views on the
purpose of an "exception framework" in the context of a library
like CM.
Perhaps you could restate your proposal (on another thread?), and
ask explicitly if people agree with the principle.
If in the affirmative, you shoul
On Thu, 24 Dec 2015 09:36:34 +0100, Luc Maisonobe wrote:
Le 24/12/2015 01:41, Gilles a écrit :
On Wed, 23 Dec 2015 20:18:10 +0100, Luc Maisonobe wrote:
Le 23/12/2015 14:32, Gilles a écrit :
Hello.
On Wed, 23 Dec 2015 10:38:03 +0100, luc wrote:
Le 2015-12-23 01:41, Gilles a écrit :
On Tue, 2
Le 24/12/2015 01:41, Gilles a écrit :
> On Wed, 23 Dec 2015 20:18:10 +0100, Luc Maisonobe wrote:
>> Le 23/12/2015 14:32, Gilles a écrit :
>>> Hello.
>>>
>>> On Wed, 23 Dec 2015 10:38:03 +0100, luc wrote:
Le 2015-12-23 01:41, Gilles a écrit :
> On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy
On Wed, 23 Dec 2015 20:18:10 +0100, Luc Maisonobe wrote:
Le 23/12/2015 14:32, Gilles a écrit :
Hello.
On Wed, 23 Dec 2015 10:38:03 +0100, luc wrote:
Le 2015-12-23 01:41, Gilles a écrit :
On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy wrote:
On 12/22/2015 11:46 AM, Gilles wrote:
Hi.
On Mon, 2
Le 23/12/2015 14:32, Gilles a écrit :
> Hello.
>
> On Wed, 23 Dec 2015 10:38:03 +0100, luc wrote:
>> Le 2015-12-23 01:41, Gilles a écrit :
>>> On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy wrote:
On 12/22/2015 11:46 AM, Gilles wrote:
> Hi.
> On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ers
[...]
On 12/23/2015 03:38 AM, luc wrote:
interface ExceptionLocalizer {
/** Localize an exception message.
* @param locale locale to use
* @param me exception to localize
* @return localized message for the exception
*/
String localize(Locale locale, MathExcept
[...]
Looks good. Where is the code? ;-)
So CM clients would:
catch(MathException e) {
String exceptionTemplate = ResourceBundle.getBundle("cm.exception.templates", new
Locale("en", "US")).getString(e.getType());
String i18Nmessage = buildMessage(exceptionTemplate, e.getContext());
Hello.
On Wed, 23 Dec 2015 10:38:03 +0100, luc wrote:
Le 2015-12-23 01:41, Gilles a écrit :
On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy wrote:
On 12/22/2015 11:46 AM, Gilles wrote:
Hi.
On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ersoy wrote:
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 De
Le 2015-12-23 01:41, Gilles a écrit :
On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy wrote:
On 12/22/2015 11:46 AM, Gilles wrote:
Hi.
On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ersoy wrote:
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was con
On Tue, 22 Dec 2015 13:17:16 -0600, Ole Ersoy wrote:
On 12/22/2015 11:46 AM, Gilles wrote:
Hi.
On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ersoy wrote:
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was considering jumping into the JDKRandomGene
On 12/22/2015 11:46 AM, Gilles wrote:
Hi.
On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ersoy wrote:
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was considering jumping into the JDKRandomGenerator exception
discussion, but I did not want to hi
Hi.
On Mon, 21 Dec 2015 22:44:16 -0600, Ole Ersoy wrote:
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was considering jumping into the JDKRandomGenerator exception
discussion, but I did not want to hijack it.
Not sure if any of you have had
On 12/21/2015 06:44 PM, Gilles wrote:
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was considering jumping into the JDKRandomGenerator exception
discussion, but I did not want to hijack it.
Not sure if any of you have had a chance to looks at this:
https://github.com/firefly-ma
On Mon, 21 Dec 2015 12:14:16 -0600, Ole Ersoy wrote:
Hi,
I was considering jumping into the JDKRandomGenerator exception
discussion, but I did not want to hijack it.
Not sure if any of you have had a chance to looks at this:
https://github.com/firefly-math/firefly-math-exceptions/
https://gith
19 matches
Mail list logo
