🚀 go-pugleaf

In <41irqv$t83@usenet.ucs.indiana.edu>, sgoehrin@copper.ucs.indiana.edu (scott goehring) writes:
>steven bourne's memory management scheme for bourne shell was to just
>write the memory and, if you get a sigsegv, sbrk some more memory and
>restart.  works fine on a PDP-11.  not so good on other architectures.

	Just wondering what is the problem with this strategy. Admittedly it is
somewhat unconventional, but it is just implementing a form of user-level VM.
Instead of realloc()ing, which I find to be very messy and inefficient, for a
growing contiguous data structure, Bourne's method seems to be what you want.
Don't know what examples you are thinking of that make this not good.
Interdata perhaps. But a decent architecture should allow growing memory
requirements and growing stacks as well.