Oziphantom wrote:I've been stung by this soooo many times, I got the assembler dev to add a warning to the assembler for me. Never again!
I've been thinking of writing my own assembler, since I can't seem to find one picky enough to stop me doing dumb stuff. Maybe I should start a thread for common bugs I should make it look out for?Gilbert wrote:Yeah. I think missing #s is a very common mistake in 6502 assembly in general, and it's sometimes hard to spot, in which in some cases the stuff still work most of the time(such as what I once encountered in my short demo).
Oziphantom wrote:Code: Select all
{ int SomeVar = something bunch of code here } int thing = SomeVar + otherThing.
How did that compile. Why did that compile. Who wrote that compiler!?
Me too! We should start a C-haters club.Bregalad wrote:I'm glad someone finally agrees with me on this.
I kid. Though in all seriousness, I think the reason it's so popular is that every major OS is written in it. Thus anyone wanting to write code for any popular platform has to deal with it at some level. And anyone who writes an OS in anything else is forced to provide compatibility or fade into obscurity.
I've looked at loads of other programming languages in search of an alternative, but they all have one thing in common: they're not freestanding. They've all got great big libraries full of exception handling, garbage collection and Shinki knows what else that they haul around everywhere. The only people who are interested in freestanding programming languages are the OS devs, and they're all using stuff like C, because everyone uses C for OS development. It's a vicious cycle.
I've been trying to break the cycle - for me at least - by coming up with a freestanding language that's safer/stricter than C, but I'm a self-taught high school dropout. What would I know.