Re: Arithmetic overflow checking
- From: "MikeP" <mp011011@xxxxxxxx>
- Date: Fri, 15 Jul 2011 23:29:43 -0500
Patricia Shanahan wrote:
On 7/14/2011 10:14 PM, MikeP wrote:
Patricia Shanahan wrote:
On 7/6/2011 8:35 AM, rop rop wrote:
If I want to have arithmetic-overflow checking in all parts of an
what is the most practical, simple, efficient way to achieve this?
Write the application in Ada.
But C# is very Java-like and has "checked" and also the
compiler-level equivalent, so C# would be the better alternative.
(And yes, I do know you were just kidding about Ada).
No, I was not really joking, though I did not attempt to find all the
languages that would meet the stated requirement.
Don't look now, but if you weren't joking, then you recommended Ada to a
Java programmer! Oh my.
I'm very strongly of the opinion different languages should provide
different features, making different trade-offs, and programmers
should pick the language for a job based on its requirements and
You have to admit, it's quite a chasm between Java/C# and Ada.
The alternative a lot of programmers follow seems to be to pick one
I do/did that. (C++ is my poison).
ignore all the others,
I have regularly looked at other languages and used them in minor ways
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.
I have no problem with pushing minor changes and additional features
within the general framework of a language, but if the basic framework
is not a good match for a job, the solution is to pick a language that
is more suitable.
C# will fit in a lot of places where Java does (or so I assume given what
I know about them, as I'm don't use either language other than for
evaluation and case study). Pushing away programmers to other languages
instead of evolving the language according to the expectations (i.e.,
what programmers have come to expect to be standard feature in a given
class of language) is surely a path to obsolescence.
- Prev by Date: Re: Need help with Unsatisfied Link Error
- Next by Date: Re: Arithmetic overflow checking
- Previous by thread: Re: Arithmetic overflow checking
- Next by thread: Re: Arithmetic overflow checking