Re: Arithmetic overflow checking
- From: Arne Vajhøj <arne@xxxxxxxxxx>
- Date: Wed, 20 Jul 2011 22:09:42 -0400
On 7/16/2011 12:29 AM, MikeP wrote:
Patricia Shanahan wrote:and then complain when there is a
mismatch between that language's features and their current
In another post, I said that I think that today (like in right now) the
awareness of the overflow issue (language support) has achieved critical
mass. Combine that with the alternatives that are available and more yet
to come, a language cannot afford to go the path of, say, C anymore for
it will lose relevance much more quickly. It's not complaining. It's
customer feedback (companies BEG their customers for such!). Companies
that don't recognize their customers needs and change with the times, go
out of business. Java is not C and can't afford to stagnate like C did
(OK, C++ gave it a "reconditioning"), or it won't last.
It seems highly unlikely that the lack of overflow detection
will have any impact on the usage of Java.
The typical business app does not care.
- Prev by Date: Re: Arithmetic overflow checking
- Next by Date: Re: Arithmetic overflow checking
- Previous by thread: Re: Arithmetic overflow checking
- Next by thread: Re: Arithmetic overflow checking