Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mitchalsup@aol.com (MitchAlsup1)
Newsgroups: comp.arch
Subject: Re: 80286 protected mode
Date: Wed, 16 Oct 2024 22:18:49 +0000
Organization: Rocksolid Light
Message-ID: <08f6b8a4fe6331c87971d285ff906d32@www.novabbs.org>
References: <2024Oct6.150415@mips.complang.tuwien.ac.at> <memo.20241006163428.19028W@jgd.cix.co.uk> <2024Oct7.093314@mips.complang.tuwien.ac.at> <7c8e5c75ce0f1e7c95ec3ae4bdbc9249@www.novabbs.org> <2024Oct8.092821@mips.complang.tuwien.ac.at> <ve5ek3$2jamt$1@dont-email.me> <be506ccef76d682d13205c69c761a086@www.novabbs.org> <ve6oiq$2pag3$1@dont-email.me> <ve6tv7$2q6d5$1@dont-email.me> <86y12uy8ku.fsf@linuxsc.com> <jwv34kx5afd.fsf-monnier+comp.arch@gnu.org> <3f2cb127c8d5dc2381fc80631a495e3e@www.novabbs.org> <8HBPO.471560$_o_3.464389@fx17.iad> <d8cffb389b3fd055ee70e87da9a3403a@www.novabbs.org> <vep60r$2ck8s$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="2354239"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="o5SwNDfMfYu6Mv4wwLiW6e/jbA93UAdzFodw5PEa6eU";
User-Agent: Rocksolid Light
X-Rslight-Site: $2y$10$7yo9SMc.1uac08vjHkrS9eVySr1YWMuqwKNkdBn/JFLYIF/nkBq.O
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: cb29269328a20fe5719ed6a1c397e21f651bda71
Bytes: 2344
Lines: 20

On Wed, 16 Oct 2024 20:00:27 +0000, Thomas Koenig wrote:

> MitchAlsup1 <mitchalsup@aol.com> schrieb:
>
>> The paragraaph with 3 >'s indicates malloc() cannot be written
>> in std. C. It used to be written in std. K&R C. I am not asking
>> if it is still in the std libraries, I am asking what happened
>> to make it impossible to write malloc() in std. C ?!?
>
> You need to reserve memory by some way from the operating system,
> which is, by necessity, outside of the scope of C (via brk(),
> GETMAIN, mmap() or whatever).

Agreed, but once you HAVE a way of getting memory (by whatever name)
you can write malloc in std. C.

> But more problematic is the implementation of free() without
> knowing how to compare pointers.

Never wrote a program that actually needs free--I have re-written
programs that used free to avoid using free, though.