8086 memory space was: The Soul of Barb's New Machine 1156
8086 memory space was: The Soul of Barb's New Machine 1158
And "executeable" file may consist of one or more of the following "block" types: Executeable - being pure machine instructions which may only be referenced by the program counter in user mode (i.e...
emoticon gets sudden cold shower Ewww..I don't like that. A goodly part of a program is to ensure that static values (or messages) stay that way. Another large part is to keep this with the proper EXE file. Depending on how the EXE is built, all of that so-called data can be different.
8086 memory space was: The Soul of Barb's New Machine 1157
This was implemented in OpenBSD a few minor versions ago. (3.3?) Primos also got it a few versions after BIND was introduced; (20.2?) Didn't Multics (eventually) implement this right? What extra cost...
I can see why you want this. How am I supposed to test my little programs if I can't feed them garbage? How do we teach the kiddies about garbage if they're never allowed to play with it? This is more important: I don't see how any OS can decide the difference between code and data until the user makes the determination. That was one of the strengths of the -10. We left most of the decisions to the user or the sysadmin or the developer. Who got the last say depended on the system, the privs, and a whole bunch of other things.
I find it repugnant when the monitor has to be changed and reloaded in order for a mere user, who is one of thousands, to play with his bits.
Subtract a hundred and four for e-mail.
Alt Folklore Computers Newsgroups