summaryrefslogtreecommitdiffstatshomepage
path: root/src/emu/memarray.h
diff options
context:
space:
mode:
author Miodrag Milanovic <mmicko@gmail.com>2013-09-17 06:47:03 +0000
committer Miodrag Milanovic <mmicko@gmail.com>2013-09-17 06:47:03 +0000
commit96aa5e1c086b4927456dc88b925d8ec112f0482e (patch)
treef59d136c51d4a065f39e3ab0d73981526c4d156b /src/emu/memarray.h
parenta7d12daf5b4c3374e8ad47a003ac7fff73d5c8fc (diff)
Cleanups and version bumpmame0150
Diffstat (limited to 'src/emu/memarray.h')
-rw-r--r--src/emu/memarray.h20
1 files changed, 10 insertions, 10 deletions
diff --git a/src/emu/memarray.h b/src/emu/memarray.h
index c1acc53e5c6..39d2b0b54e2 100644
--- a/src/emu/memarray.h
+++ b/src/emu/memarray.h
@@ -37,16 +37,16 @@
****************************************************************************
- A memory array in this case is an array of 8, 16, or 32-bit data
- arranged logically.
-
- A memory array is stored in "natural" order, i.e., read/writes to it
- are done via AM_RAM, or standard COMBINE_DATA, even if the width of
- the CPU is different from the array width.
-
- The read_entry/write_entry functions serve to read/write entries of
- the configured size regardless of the underlay width of the CPU's
- memory system.
+ A memory array in this case is an array of 8, 16, or 32-bit data
+ arranged logically.
+
+ A memory array is stored in "natural" order, i.e., read/writes to it
+ are done via AM_RAM, or standard COMBINE_DATA, even if the width of
+ the CPU is different from the array width.
+
+ The read_entry/write_entry functions serve to read/write entries of
+ the configured size regardless of the underlay width of the CPU's
+ memory system.
***************************************************************************/