nesdev.org

If you don't mind reinventing the wheel (writing your own parser) once you have the workings well defined, a VRML-style syntax would avoid quoting everything, comma separation between properties, and the need to put code in strings.

I didn't even know this was a thing. I've sometimes missed clicking the bookmarks toolbar in Firefox and ended up middle-click-pasting the same url into the middle of itself in the address bar. Not a clue what was happening (other than maybe Firefox constantly putting the url in the clipboard or som...

yeah, I was confusing his assembler feature with the talk of the global jmp/label ret.

Nevermind me. I get it now and could see it going either way.

1. By far my most common label is a @Return: label in front of a nearby RTS statement. Maybe it's my style of coding, but I find that subroutines always has some branching conditions that exits early. So I realized it would be pretty nifty if I could just write a branch jump like this: LDA MyVar BE...

Some compilers (GCC in particular) will even optimize some loops into calls to memcpy/move/set functions.

Visual C++ for Windows Store/UWP apps is currently stuck using their proprietary C++/CX language that auto generates opaque regular C++ behind the scenes. They do plan to convert over to a new C++/Winrt "projection" that allows for native C++20 (so much co_await!). There's a github page he...

On Linux, dynamic libraries have the '.so' extension (for 'shared object') and are also what you link with. For me on Ubuntu (which I *think* installed with the command tepples gave, it's been awhile), the include is "#include <SDL2/SDL.h>" and then the link command has `pkg-config --cflag...

If it's just a gcc cross compiler, binutils (which has an assembler) will likely be in there somewhere as it has the linker.
You could also compile binutils yourself targeting arm.

That's one option. It takes being careful about when various things trigger catch up, like sprite-0-hit. In my case, I just chose to write my cpu as NES-specific as it has calls to ppu_cycles(3) throughout instructions after emulating each cycle, although sometimes that's not necessary as not every ...

That would not work for some instructions as it doesn't represent the two happening at the same time. For example, read-modify-write instructions (from nesdev.com/6502_cpu.txt): Read-Modify-Write instructions (ASL, LSR, ROL, ROR, INC, DEC, SLO, SRE, RLA, RRA, ISB, DCP) # address R/W description --- ...

Its tricky as the 5th is actually the 1st of the next opcode. So it depends on how your system is implemented but basically it only takes 4 cycles max, as the fetch opcode is the first cycle of the next opcode. bne takenNextPage - 1 load bne 1 - 2 load offset 2 - 3 add PCL 3 - 4 add PCH 4 takenNext...

(quietly updates his emulator to not have taken branches to a different page take 5 cycles)

I'm not sure if Form.Show() and Application.DoEvents() will work together (it's been forever since I've used C#), but maybe try: form.Show(); while( form not closed ) { //render Application.DoEvents(); } If it'll work like that you won't really need to override WndProc. Any code that comes after th...

I'm not sure if Form.Show() and Application.DoEvents() will work together (it's been forever since I've used C#), but maybe try:

form.Show();

while( form not closed )
{
//render
Application.DoEvents();
}

If it'll work like that you won't really need to override WndProc.