I've been considering some methods by which phobos can be enhanced, and have
come up with  a couple of ideas.
1. std.c OS-specific stuff  could be moved out of std, and we could create a
new sys tree; sys.linux, sys.windows, sys.bsd, etc.  This way, C standard
stuff goes under std.c, and everything else that is system-specific goes
under sys.
2. In my opinion, the etc tree is somewhat underused.  What we could do is
put in std only those core things that (1) we deam essential to any D setup
and (2) don't need any other external library (besides the c library of
course).  Thus, std.zlib and std.recls would become etc.zlib and etc.recls,
something which makes a bit of sense since we already have etc.c.zlib.

-- 



Ameer
---
Visit my blog at
http://ameerarmaly.blogspot.com
---
Life is either tragedy or comedy.
 Usually it's your choice. You can whine or you can laugh.
--Animorphs

On Mon, 24 Oct 2005 15:48:03 -0400, Ameer Armaly wrote:

> I've been considering some methods by which phobos can be enhanced, and have
> come up with  a couple of ideas.
> 1. std.c OS-specific stuff  could be moved out of std, and we could create a
> new sys tree; sys.linux, sys.windows, sys.bsd, etc.  This way, C standard
> stuff goes under std.c, and everything else that is system-specific goes
> under sys.
> 2. In my opinion, the etc tree is somewhat underused.  What we could do is
> put in std only those core things that (1) we deam essential to any D setup
> and (2) don't need any other external library (besides the c library of
> course).  Thus, std.zlib and std.recls would become etc.zlib and etc.recls,
> something which makes a bit of sense since we already have etc.c.zlib.

I get the following from
http://all-technology.com/eigenpolls/bpfsd/index.php?it=17
on http://all-technology.com/eigenpolls/bpfsd/ and I am wondering
if we could use it here maybe make a Domain, Technical and Platform layer.


Use an Layered software Architecture

Something like

1) Interface Layer
This is the applications interface to the outside world
it could handle input from a gui or a data stream.

2) Application Layer

Here you put all the application specific code.
Sometime called the model layer.

3) Domain Layer
Here you put domain specific and application independent code.

sometime called the business rules layer.

4) Technical Layer
Typical math, XML and other standard libraries.

5) Platform Layer
This is the Platform specific code like Databases, communication
and OS specific functions.

An layer should only depend on layers below it self
and ideally only on the layer just below it self.