> I'm just going for a workable system, having long since given up on perfection. Let's just cut & print and move on to more interesting things!

You mean like std.c.recls? :)

Walter wrote:
> 
> There have been a lot of good ideas and points made about this in the
> discussions here. The upshot is there isn't a single right answer,
> but there are a few clearly wrong ones <g>. So it's up to me to just pick
> one of the right answers.
> 
> So here goes:
> 
> std
>  Contains the 'standard' modules that will be available on all
>  implementations of D. Emphasis in this package will be on reliability,
>  stability, and portability. std as a name has the advantage of being used
>  in C++ to specify the standard library, and so is familiar and highly
>  unlikely to conflict with common variable names.

That's a good decision.

By what formal or informal procedure can one contribute modules?

-- 
Helmut Leitner    leitner@hls.via.at
Graz, Austria   www.hls-software.com

Walter wrote:
> std
> ...

Just to keep track:
   <http://www.prowiki.org/wiki4d/wiki.cgi?StandardLibrary/Layout>

-- 
Helmut Leitner    leitner@hls.via.at
Graz, Austria   www.hls-software.com

"Matthew Wilson" <matthew-hat@-stlsoft-dot.-org> wrote in message news:bnnlgq$28ib$1@digitaldaemon.com...
> Isn't it a language feature, rather than a library feature?
>
> Maybe thread wasn't the best example. The class info stuff?

The line between can get pretty fuzzy at times. The os packages clearly mark using them as non-portable, but I don't see the equivalent value added for dividing between language and library.

"Helmut Leitner" <helmut.leitner@chello.at> wrote in message news:3F9F6104.A4076357@chello.at...
> That's a good decision.

Thank-you.

> By what formal or informal procedure can one contribute modules?

Certainly, it's informal. Which means any way you want to <g>.

"Helmut Leitner" <helmut.leitner@chello.at> wrote in message news:3F9F6290.6FB11680@chello.at...
>
>
> Walter wrote:
> > std
> > ...
>
> Just to keep track:
>    <http://www.prowiki.org/wiki4d/wiki.cgi?StandardLibrary/Layout>

Nice. Thanks for keeping that up to date!

> > Just to keep track:
> >    <http://www.prowiki.org/wiki4d/wiki.cgi?StandardLibrary/Layout>


May suggest:

Original:
--------------------
std.os
    Access to platform specific functionality.

std.os.windows
    Specific to win32 and win64 operating systems. (win64 is coming, so calling it
    ...

std.os.linux
    Specific to linux operating systems. (StdOsLinuxComments)
--------------------

Modified:
--------------------
std.os
    Access to OS-level, platform-independent functionality.

std.os.windows
    ...
...
--------------------

Or do I misunderstand something?

(Sorry I just dind't dare Editing directly in the Wiki.
I'm a shy one... :) )

Cheers,
Sz.

> May suggest:
>
> Original:
> --------------------
> std.os
>     Access to platform specific functionality.
>
> std.os.windows
>     Specific to win32 and win64 operating systems. (win64 is coming, so
calling it
>     ...
>
> std.os.linux
>     Specific to linux operating systems. (StdOsLinuxComments)
> --------------------
>
> Modified:
> --------------------
> std.os
>     Access to OS-level, platform-independent functionality.
>
> std.os.windows
>     ...
> ...
> --------------------

Good point.

> Or do I misunderstand something?
>
> (Sorry I just dind't dare Editing directly in the Wiki.
> I'm a shy one... :) )

LOL

Luna Kid wrote:

>>>Just to keep track:
>>>   <http://www.prowiki.org/wiki4d/wiki.cgi?StandardLibrary/Layout>
> 
> May suggest:
> 
> Original:
> --------------------
> std.os
>     Access to platform specific functionality.
>     ...
> 
> 
> Modified:
> --------------------
> std.os
>     Access to OS-level, platform-independent functionality.
>     ...
> 
> Or do I misunderstand something?
I think you do.

The way I read it, "std.os" would only contain code that relates to platform-dependent (a/k/a platform-specific) functionality.  It would probably contain only a series of directories: "windows", "linux", and any other platforms with D implementations.

The platform-independent code would reside elsewhere in "std", "internal", or "etc".

> 
> (Sorry I just dind't dare Editing directly in the Wiki.
> I'm a shy one... :) )

Don't be afaid to edit the Wiki stuff.  That's what Wiki's are designed for.  They're easy to edit and they're easy to change back.

Justin

> 
> Cheers,
> Sz.
> 
> 

In article <bnn9a0$1o09$1@digitaldaemon.com>, Walter says... [...]
>etc
> There are lots of 'other' modules for D, and right now there is no
> organized way to deal with them. There needs to be a place for them.
> The etc heirarchy will mirror the standard one, i.e. there will
> be etc.c, etc.os.windows, ... These will not be official parts of D
> nor will they be standardized. However, candidates for standardization
> will be drawn from etc. etc is the place for
> not-quite-there-yet-but-still-useful modules.

What does 'etc' stand for?
I'd prefer 'ext', that means extension.

Ciao