@Jonathan_Blow It strikes me that the author has probably never programmed in assembler, or he'd realise how computers actually work.
-
-
Replying to @grumpygiant
@Jonathan_Blow In particular, "mov eax, [ebx+0]" is the same as "mov eax, [ebx]". This is important.1 reply 0 retweets 1 like -
Replying to @grumpygiant
@grumpygiant@Jonathan_Blow It all seemed very dubious to me. Compile-time indexing isn't the interesting part, it's variables, right?2 replies 0 retweets 1 like -
Replying to @cmuratori
@grumpygiant@Jonathan_Blow So to make sure you don't have to dec-by-one before each indexing op, you'd have to pre-back-up your pointers?1 reply 0 retweets 1 like -
Replying to @cmuratori
@grumpygiant@Jonathan_Blow Seems like you really wouldn't want to do that, regardless of the history, but maybe I'm missing something.1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@Jonathan_Blow Yep. People care what the "compiler" is doing for you, but really it's what the "machine" is doing that matters.1 reply 0 retweets 2 likes -
Replying to @grumpygiant
@cmuratori@Jonathan_Blow I mean why not 37-based indexing? The compiler would take care of it, right?2 replies 0 retweets 1 like
@grumpygiant @Jonathan_Blow 37-based indexing is clearly the right theoretical approach.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.