Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: comp.arch Subject: Re: 80286 protected mode Date: Mon, 21 Oct 2024 14:04:42 -0400 Organization: A noiseless patient Spider Lines: 18 Message-ID: References: <2024Oct6.150415@mips.complang.tuwien.ac.at> <2024Oct7.093314@mips.complang.tuwien.ac.at> <7c8e5c75ce0f1e7c95ec3ae4bdbc9249@www.novabbs.org> <2024Oct8.092821@mips.complang.tuwien.ac.at> <86y12uy8ku.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Mon, 21 Oct 2024 20:04:50 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a343ee786601adc72d457eb7c4cee3f6"; logging-data="1109395"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/gfxMQFb7OYmZBIQf9OlYfPYB9d6ic1WE=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:xs7UmUbvS/urOC4/JzNaLD9ErhI= sha1:+gpdWPeiv5NSBhLuLJoIol+a0Pc= Bytes: 2308 >>> I don't see an advantage in being able to implement them in standard C. >> It means you can likely also implement a related yet different API >> without having your code "demoted" to non-standard. > That makes no sense to me. We are talking about implementing standard > library functions. If you want to implement other functions, go ahead. No, I'm talking about a very general principle that applies to languages, libraries, etc... For example, in Emacs I always try [and don't always succeed] to make sure that the default behavior for a given functionality can be implemented using the official API entry points of the underlying library, because it makes it more likely that whoever wants to replace that behavior with something else will be able to do it without having to break abstraction barriers. Stefan