Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #86733

Re: Python Worst Practices

Date 2015-03-02 08:12 -0500
From Dave Angel <davea@davea.name>
Subject Re: Python Worst Practices
References (7 earlier) <CAPTjJmoRiTb+gL8BVKHLzGCfPkjXjX1_jU_Osu2FYkUxjC0Aqg@mail.gmail.com> <mif7fadg0g1b276shsagrg2urvonfbbnd8@4ax.com> <54F3C3FF.3040608@mrabarnett.plus.com> <54F3EBF5.3030701@davea.name> <54F459DE.8020706@mrabarnett.plus.com>
Newsgroups comp.lang.python
Message-ID <mailman.37.1425301988.13471.python-list@python.org> (permalink)

Show all headers | View raw


On 03/02/2015 07:38 AM, MRAB wrote:
> On 2015-03-02 04:49, Dave Angel wrote:
>> On 03/01/2015 08:59 PM, MRAB wrote:
>>> On 2015-03-02 01:37, Dennis Lee Bieber wrote
>>>>

>>
>> The 16 bit address bus permitted addressing of 64k words.  On most
>> processors, that was 64k bytes, though I know one Harris had no bytes,
>> but every memory access was 16 bits.  It therefore had the equivalent of
>> 128k bytes.  Likewise I believe some of the DEC and DG minis had 128k
>> bytes of addressability.
>>
> I have (or had, not sure where it is!) a manual of the TMS9900
> processor, and I'm sure it addresses 64k _bytes_.
>
> Wikipedia says "65,536 bytes or 32,768 words".
>

Like I said, on most processors, it was 64k bytes.

interestingly enough I know of one architecture which used 128k for the 
8-bit Z80, even though that processor only had 16 address lines.  Being 
a server, the code was mostly static, and fit in 64k.  But they also 
wanted 64k for data.  So they used one of the processor status lines as 
a select between two banks of memory. When the processor was fetching an 
instruction, it got it from bank 0, while if it was fetching or writing 
data, it went to bank 1.  Obviously they had a mode where it read and 
wrote from bank 0 as data, both for bootstrapping, and for overlays or 
whatever.


-- 
DaveA

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Python Worst Practices Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-02-28 15:33 +0000
  Re: Python Worst Practices BartC <bc@freeuk.com> - 2015-02-28 17:55 +0000
    Re: Python Worst Practices Mark Lawrence <breamoreboy@yahoo.co.uk> - 2015-02-28 18:38 +0000
    Re: Python Worst Practices Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2015-03-01 13:08 +1100
      Re: Python Worst Practices Chris Angelico <rosuav@gmail.com> - 2015-03-01 13:43 +1100
      Re: Python Worst Practices BartC <bc@freeuk.com> - 2015-03-01 12:47 +0000
      Re: Python Worst Practices Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-03-01 20:37 -0500
      Re: Python Worst Practices MRAB <python@mrabarnett.plus.com> - 2015-03-02 01:59 +0000
      Re: Python Worst Practices Dave Angel <davea@davea.name> - 2015-03-01 23:49 -0500
      Re: Python Worst Practices MRAB <python@mrabarnett.plus.com> - 2015-03-02 12:38 +0000
      Re: Python Worst Practices Dave Angel <davea@davea.name> - 2015-03-02 08:12 -0500
      Re: Python Worst Practices Jonas Wielicki <jonas@wielicki.name> - 2015-03-06 07:58 +0100
      Re: Python Worst Practices Chris Angelico <rosuav@gmail.com> - 2015-03-06 21:09 +1100
        Re: Python Worst Practices Mario Figueiredo <marfig@gmail.com> - 2015-03-07 16:11 +0100

csiph-web