On Sat, 14 Oct 2017 01:48:44 +1300, Gregory Ewing wrote:
> Steve D'Aprano wrote:
>> I wasn't questioning where the data came from, but how the compiler can
>> write to READ ONLY MEMORY which might not even be in the same continent
>> as the compiler that generated the code.
>
> I thought it would be fairly obvious that by "put it in read-only
> memory" I meant "arrange for it to be in a location that is read-only at
> run time". Obviously it can't be read-only at *compile* time, just as a
> physical ROM can't be read-only at manufacture time.
oh yes it can
in the past for large quantitys the data in a ROM chip was part of the
chip etching mask (unless you consider a blank silicon wafer to be
"Programmable" by the etching process)rather than prom which used
programmable fuses or prom which could be erased by UV light (assuming
the chip was fitted with a window otherwise it was known as one time
programmable EPROM)
The Apollo lunar lander used a magnetic core store that was hard coded at
the time it was "Woven"
I doubt that either process is in widespread usage any longer as most
manufacturers no incorporate a way to update the firmware of a device
(usually with flash memory)
--
"I am not sure what this is, but an `F' would only dignify it."
-- English Professor
--
https://mail.python.org/mailman/listinfo/python-list
