Originally posted by Disch

---

Case insensitiviy is what's stupid. 'c' and 'C' are two clearly different characters

---

Originally posted by Gavin

---

It would seem most logical that many conventions stay true to what a computer essentially is and how it interprets data, instead of obscuring it.

---

Originally posted by Disch

---

Originally posted by creaothceann

---

"Btn_CopyTxt" and "btn_copytxt" clearly refer to the same thing.

---

They might... but they're 2 different strings. Having 2 different strings refer to the same variable is not only confusing, but sloppy. Even if the language was case insensitive it would be bad practice.

And besides... case sometimes does play a major role in distinguishing between types. For example in C, I often do:

HWND hWnd;

"HWND" being the variable type, "hWnd" being the name of my variable (in hungarian notation... the preceeding 'h' indicates that this variable is a handle, and 'Wnd' is the name of the variable). I also often do HWAVEOUT hWaveout, HINSTANCE hInstance, MSG msg, etc.

---

Originally posted by Disch

---

---

Case sensitiviy is a great source of possible misunderstandings.

---

I can't even comprehend how you figure this.

---

Originally posted by Disch

---

---

Sure, for the compiler it's easier to distinguish, but a compiler should make the programmer's life easier (when possible), not the other way around.

---

No, see... the job of the compiler is to take the code that you write and compile it. It's not supposed to guess what you're trying to say and compile an interpretted version of it. You're supposed to tell it exactly what you want. Next thing you know you'll be saying it should be doing spell check errors and that "button" and "buton" are clearly trying to reference the same variable. For heaven's sake I hope it never comes to that.

If the variable name is "var"... refer to it that way. If you don't want to refer to it that way... change the variable name.

---

Originally posted by Disch

---

But the fact of the matter is... uppercase letters and lowercase letters are different. They are... it's not disputable. They look different... they have different contexts, and they're represented differently by the machine. There is no reason why the machine should treat 2 different characters like they're exactly the same... it just doesn't make sense.

---

Originally posted by Squash Monster

---

And I always figured that a compiler would take your booleans and store eight to a byte and sort out the details on its own.

---

KeyOnStA	db 0
KeyOnStB	db 0

SDD1BankA	db 0
SDD1BankB	db 0
SDD1BankC	db 0
SDD1BankD	db 0
vramread2	db 0	; previous character for vram read
nosprincr	db 0
poamaddrs	dw 0
ioportval	db 0
iohvlatch	db 0
ppustatus	db 0

Originally posted by creaothceann

---

This should be at offset 0090F1EF.

---

Originally posted by Gideon Zhi

---

The 32 kilobytes following ($20C13-$28C12) are where VRAM is stored. This is mainly picture data, but there's tilemap stuff in there too - could be useful if you're trying to find layout data in a ROM. The rest of it I'm not sure about - some of it contains the graphical data for the preview, and I'm not sure where the sprite tables get stored. That'd probably be something useful for me to learn at some point...

---

Originally posted by Juggling Joker

---

Note! Until I allow for dynamic memory allocation, do NOT load very large files.

---