Deutsch   English   Français   Italiano  
<ve7rv0$31th1$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: David Brown <david.brown@hesbynett.no>
Newsgroups: comp.arch
Subject: Re: 80286 protected mode
Date: Thu, 10 Oct 2024 08:24:32 +0200
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <ve7rv0$31th1$1@dont-email.me>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 10 Oct 2024 08:24:32 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="a48c12dce33700a9986218db92a85cb4";
	logging-data="3208737"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/AZMNFvZsCSb0FXCTwMq+ijbYXkP6wh1Q="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
Cancel-Lock: sha1:j5leJRIN2KWqTKCGPY2NqP3tBrY=
In-Reply-To: <ve6tv7$2q6d5$1@dont-email.me>
Content-Language: en-GB
Bytes: 2512

On 09/10/2024 23:52, Stephen Fuld wrote:
> On 10/9/2024 1:20 PM, David Brown wrote:

>> There are lots of parts of the standard C library that cannot be 
>> written completely in portable standard C.  (How would you write a 
>> function that handles files?  You need non-portable OS calls.)  That's 
>> why these things are in the standard library in the first place.
> 
> I agree with everything you say up until the last sentence.  There are 
> several languages, mostly older ones like Fortran and COBOL, where the 
> file handling/I/O are defined portably within the language proper, not 
> in a separate library.  It just moves the non-portable stuff from the 
> library writer (as in C) to the compiler writer (as in Fortran, COBOL, 
> etc.)
> 
> 

I meant that this is why these features have to be provided, rather than 
left for the user to implement themselves.  They could also have been 
provided in the language itself (as was done in many other languages) - 
the point is that you cannot write the file access functions in pure 
standard C.