payload: {"action":"created","issue":{"url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/12","repository_url":"https://api.github.com/repos/OneLoneCoder/olcNES","labels_url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/12/comments","events_url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/12/events","html_url":"https://github.com/OneLoneCoder/olcNES/issues/12","id":493258412,"node_id":"MDU6SXNzdWU0OTMyNTg0MTI=","number":12,"title":"Initial value of stkp during initialization","user":{"login":"d0gtail","id":45495564,"node_id":"MDQ6VXNlcjQ1NDk1NTY0","avatar_url":"https://avatars2.githubusercontent.com/u/45495564?v=4","gravatar_id":"","url":"https://api.github.com/users/d0gtail","html_url":"https://github.com/d0gtail","followers_url":"https://api.github.com/users/d0gtail/followers","following_url":"https://api.github.com/users/d0gtail/following{/other_user}","gists_url":"https://api.github.com/users/d0gtail/gists{/gist_id}","starred_url":"https://api.github.com/users/d0gtail/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/d0gtail/subscriptions","organizations_url":"https://api.github.com/users/d0gtail/orgs","repos_url":"https://api.github.com/users/d0gtail/repos","events_url":"https://api.github.com/users/d0gtail/events{/privacy}","received_events_url":"https://api.github.com/users/d0gtail/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-09-13T10:45:30Z","updated_at":"2019-09-13T22:34:54Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\nwould it be safe (for consistency) to set stkp to 0xFD during initialization like it is done when reset() is called?\r\n```c++\r\npublic:\r\n...\r\n uint8_t y = 0x00;\r\n uint8_t stkp = 0xFD;\r\n...\r\n```\r\nhttps://github.com/OneLoneCoder/olcNES/blob/5603c9a149d2bae3b2075664b370e0fdca2432df/Part%232%20-%20CPU/olc6502.h#L112-L120\r\nhttps://github.com/OneLoneCoder/olcNES/blob/5603c9a149d2bae3b2075664b370e0fdca2432df/Part%232%20-%20CPU/olc6502.cpp#L166-L171"},"comment":{"url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/comments/531411607","html_url":"https://github.com/OneLoneCoder/olcNES/issues/12#issuecomment-531411607","issue_url":"https://api.github.com/repos/OneLoneCoder/olcNES/issues/12","id":531411607,"node_id":"MDEyOklzc3VlQ29tbWVudDUzMTQxMTYwNw==","user":{"login":"OneLoneCoder","id":25419386,"node_id":"MDQ6VXNlcjI1NDE5Mzg2","avatar_url":"https://avatars3.githubusercontent.com/u/25419386?v=4","gravatar_id":"","url":"https://api.github.com/users/OneLoneCoder","html_url":"https://github.com/OneLoneCoder","followers_url":"https://api.github.com/users/OneLoneCoder/followers","following_url":"https://api.github.com/users/OneLoneCoder/following{/other_user}","gists_url":"https://api.github.com/users/OneLoneCoder/gists{/gist_id}","starred_url":"https://api.github.com/users/OneLoneCoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/OneLoneCoder/subscriptions","organizations_url":"https://api.github.com/users/OneLoneCoder/orgs","repos_url":"https://api.github.com/users/OneLoneCoder/repos","events_url":"https://api.github.com/users/OneLoneCoder/events{/privacy}","received_events_url":"https://api.github.com/users/OneLoneCoder/received_events","type":"User","site_admin":false},"created_at":"2019-09-13T22:34:54Z","updated_at":"2019-09-13T22:34:54Z","author_association":"OWNER","body":"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."}}
other: {"actor":{"display_login":"OneLoneCoder"}}