Re: NASM 0.98.39 vs. NASM 2.03.01 disassembly


Alexei A. Frounze remote read my brain:

Rod Pemberton posted:...
Look at how long and how many processors have had a carry flag.
It's been there since the beginning of microprocessors, yet you can't
easily check for integer overflow in C.

Right, and I may only guess why flags didn't make it into HLLs,
perhaps much too complicated for those who only got a CS-degree ? :)

I didn't know that you're are gifted with PSI :)
You posted what I think.

__
wolfgang

<q Alex>
Guys straight out of the college know too little these days, unless
they're true geeks and they've gone far beyond what was given in
class. By this same logic, for them we should've eliminated the
complex type system in HLLs and only have kept one numerical type of a
fixed bit size: an unsigned integer. Anything that involves signed
values or floating-point numbers is usually too complicated or too
hard to get right. :) Oh, and, of course, all pointers should've been
removed too. You see, indirection is too complex to understand, let
alone keep track of pointer values and array indices. Maybe the arrays
should've been banned too for the sake of security. :) Now, what an
easy thing it would be to learn to and program in a language, with
only one data type (unsigned integer)!

Then again, I've seen plenty of people with lots of programming
experience (5+ years, full-time positions; with and without CS/EE/ECE
degrees, even PhDs) who've done pretty stupid inexcusable things for
someone with that much of experience. When people get the basics
right, the quality of their software greatly improves. I mean, the
bugs start to become more rare (fewer trivial, embarrassing and
irritating bugs) and more related to the actual problems that the
software is designed to solve, which makes them in a way more
interesting too.

Alex
</q>


.

Relevant Pages

  • Re: NASM 0.98.39 vs. NASM 2.03.01 disassembly
    ... fixed bit size: an unsigned integer. ... :) Oh, and, of course, all pointers should've been ... alone keep track of pointer values and array indices. ... irritating bugs) and more related to the actual problems that the ...
    (alt.lang.asm)
  • Re: Array subscripting overflow behaviour
    ... Basically an unsigned integer is being used as a ... I want to confirm my interpretation of this behaviour as there ... > and pointers are themselves really just unsigned byte numbers. ... > wrap-around of the sum exactly compensated for the earlier wrap-around of ...
    (comp.lang.c)
  • Re: Array subscripting overflow behaviour
    ... Basically an unsigned integer is being used as a ... > I want to confirm my interpretation of this behaviour as there have been ... It is officially undefined behaviour. ... because pointers and unsigned integers on your system have ...
    (comp.lang.c)
  • Re: int or bool?
    ... The idea of zero being false is much more natural, also, since it is often ... used when evaluating pointers (esp. ... A poiinter is essentially an unsigned integer value, ... Hiding that implied condition ...
    (comp.lang.cpp)
  • Re: C programming - problem with structures
    ... > ive been mucking about with structures and pointers and stuff, ... the one 'p' points to (remember, array indices start with 0 in C). ... And now you write even further over memory which isn't yours... ... the C language (but no extensions, ...
    (comp.programming)