Initial value of stkp during initialization

[d0gtail]

Hi,

would it be safe (for consistency) to set stkp to 0xFD during initialization like it is done when reset() is called?

public:
...
 uint8_t y = 0x00;
 uint8_t stkp = 0xFD;
...

olcNES/Part#2 - CPU/olc6502.h

Lines 112 to 120 in 5603c9a

	public:
	// CPU Core registers, exposed as public here for ease of access from external
	// examinors. This is all the 6502 has.
	uint8_t a = 0x00; // Accumulator Register
	uint8_t x = 0x00; // X Register
	uint8_t y = 0x00; // Y Register
	uint8_t stkp = 0x00; // Stack Pointer (points to location on bus)
	uint16_t pc = 0x0000; // Program Counter
	uint8_t status = 0x00; // Status Register

olcNES/Part#2 - CPU/olc6502.cpp

Lines 166 to 171 in 5603c9a

	// Reset internal registers
	a = 0;
	x = 0;
	y = 0;
	stkp = 0xFD;
	status = 0x00 | U;

[OneLoneCoder]

In principle yes, but philosophically no. CPUs and memories start up in unknown states, so they should always be issued a reset command. I get your point though, and it was an oversight by me.