Editing Zero page (section)

== References ==
{{Reflist|refs=
<ref name="Student Papers in Computer Architecture">{{cite book |last1=Sjödin |first1=Tomas |last2=Jonsson |first2=Johan |title=Student Papers in Computer Architecture |date=2006 |location=Umeå, Sweden |page=29 |s2cid=14355431 |url=http://pdfs.semanticscholar.org/fe94/c1e8319ee97d7649524e141a87ac2f5c8342.pdf |archive-url=https://web.archive.org/web/20190309043117/http://pdfs.semanticscholar.org/fe94/c1e8319ee97d7649524e141a87ac2f5c8342.pdf |url-status=dead |archive-date=2019-03-09 |access-date=2019-08-21}}</ref>
<ref name="msdn">{{cite web |title=Managing Virtual Memory |url=http://msdn.microsoft.com/en-us/library/ms810627.aspx |date=2014-12-05 |access-date=2014-12-05 |publisher=[[Microsoft]]}}</ref>
<ref name="drobe_ofla">{{cite web|title=ARM 'security hole' is ofla cousin |url=http://www.drobe.co.uk/article.php?id=1941 |date=2007-04-24 |access-date=2008-10-22 |publisher=drobe.co.uk}}</ref>
<ref name="Intel_1973_MCS-4">{{cite book |title=MCS-4 Assembly Language Programming Manual - The INTELLEC 4 Microcomputer System Programming Manual |chapter=4.1 Crossing Page Boundaries |edition=Preliminary |publisher=[[Intel Corporation]] |date=December 1973 |location=Santa Clara, California, USA |id=MCS-030-1273-1 |pages=((2-4, 2-14, 3-41, 4-1)) |url=http://bitsavers.trailing-edge.com/components/intel/MCS4/MCS-4_Assembly_Language_Programming_Manual_Dec73.pdf |access-date=2020-03-02 |url-status=live |archive-url=https://web.archive.org/web/20200301235541/http://bitsavers.trailing-edge.com/components/intel/MCS4/MCS-4_Assembly_Language_Programming_Manual_Dec73.pdf |archive-date=2020-03-01 |quote=[…] certain instructions function differently when located in the last byte (or bytes) of a page than when located elsewhere. […] Two addresses are on the same page if the highest order hexadecimal digit of their addresses are equal. […] If the JIN instruction is located in the last location of a page in memory, the highest 4 bits of the program counter are incremented by one, causing control to be transferred to the corresponding location on the next page. […] If […] the JIN had been located at address 255 decimal (0FF hexadecimai), control would have been transferred to address 115 hexadecimal, not 015 hexadecimal. This is dangerous programming practice, and should be avoided whenever possible. […] programs are held in either ROM or program RAM, both of which are divided into pages. Each page consists of 256 8-bit locations. Addresses 0 through 255 comprise the first page, 256-511 comprise the second page, and so on. In general, it is good programming practice to never allow program flow to cross a page boundary except by using a JUN or JMS instruction. […]}}</ref>
}}