Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.linux.misc    |    Linux-specific topics not covered by oth    |    135,536 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 135,245 of 135,536    |
|    The Natural Philosopher to Pancho    |
|    Re: Memory Safety (Re: Python: A Little     |
|    05 Feb 26 19:27:48    |
      From: tnp@invalid.invalid              On 05/02/2026 15:09, Pancho wrote:       > On 2/5/26 14:14, The Natural Philosopher wrote:       >       >> The first is of course implementation specific. C can specify a data       >> stack separate from a program stack and avoid code corruption, leaving       >> only data corruption...       >>       >       > Can it? Naively, I would have thought C was normally built on top of       > native assembler function calls, which dictates a shared stack.       > Obviously you could implement a function call independent of assembler,       > but does anyone, in practice?       >       You simply use a register as a second stack [data] pointer.              Assign all your mem variables on that stack, and increment it at       function end.              The assembler is trivial. Making C do it that way would not be hard,       either..                     --       Religion is regarded by the common people as true, by the wise as       foolish, and by the rulers as useful.              (Seneca the Younger, 65 AD)              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca