Why std.stdio and not std.io ?

Stewart Gordon smjg_1998 at yahoo.com
Tue May 9 08:55:56 PDT 2006


Jarrett Billingsley wrote:
> "Tom" <Tom_member at pathlink.com> wrote in message 
> news:e3q9ir$2i7n$1 at digitaldaemon.com...
>> Maybe it sounds as a stupid question but I still wonder why to mimic C 
>> include name for standard input/output.
> 
> This has been discussed before ;)  Same goes for std.stdarg and std.stdint. 

AIUI they couldn't have named it std.int, because int is a keyword.  But 
still, that doesn't mean there isn't a better name than stdint.

> It's probably from when the std modules didn't used to be in std, and were 
> just "import stdio;", etc.
<snip>

Was there any such time?  Either way, std.stdio didn't exist back then.

Actually, a possible explanation is that the two "std"s mean different 
things.

The first one refers to the D standard library that is Phobos.

The second refers to the standard input/output streams.

So std.stdio is the D standard library module for accessing the standard 
I/O.

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- 
PE- Y? PGP- t- 5? X? R b DI? D G e++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on 
the 'group where everyone may benefit.



More information about the Digitalmars-d-announce mailing list