Path: ...!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail From: George Neuner Newsgroups: comp.arch Subject: Re: portable malloc Date: Tue, 22 Oct 2024 17:26:06 -0400 Organization: i2pn2 (i2pn.org) Message-ID: References: <86y12uy8ku.fsf@linuxsc.com> <2cd5dcbd44d71a2b76021f7b44034143@www.novabbs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="3233524"; mail-complaints-to="usenet@i2pn2.org"; posting-account="h5eMH71iFfocGZucc+SnA0y5I+72/ecoTCcIjMd3Uww"; User-Agent: ForteAgent/8.00.32.1272 X-Spam-Checker-Version: SpamAssassin 4.0.0 Bytes: 1881 Lines: 20 On Tue, 22 Oct 2024 01:09:49 -0000 (UTC), Lawrence D'Oliveiro wrote: >On Mon, 21 Oct 2024 23:52:59 +0000, MitchAlsup1 wrote: > >> On Mon, 21 Oct 2024 23:17:10 +0000, Lawrence D'Oliveiro wrote: >> >>> On Sun, 20 Oct 2024 21:51:30 +0100, Vir Campestris wrote: >>> >>>> Because some implementations will require communication with the OS >>>> there cannot be a truly portable malloc. >>> >>> There can if you have a portable OS API. The only serious candidate for >>> that is POSIX. >> >> POSIX is an environment not an OS. > >Guess what the “OS” part of “POSIX” stands for. It's still an just environment - POSIX defines only an interface, not an implementation.