How to break module into multiple file.

[Jonathan M Davis]

> On 5/13/2011 3:51 PM, Alexander wrote:
> > On 13.05.2011 00:59, Jonathan M Davis wrote:
> >> Still, I wouldn't have though that dashes would have been a big enough
> >> deal to really care.
> >> 
> > I didn't say that this is a "big deal", just "inconvenience".
> > 
> > There are many minor things which are not a big deal, but make life a
> > bit less convenient - and this is the exact reason why we have so
> > many programming languages, libraries etc :)
> > 
> > /Alexander
> 
> I agreed with what alexander is voicing out. How about the process
> within a team development. That current D layout seem to limit that one
> file to a single developer. Instead of multiple class multiple developer
> within the same module.
> Using the example:
> HashMap & Unit tested implemented by matthew
> LinkedList & Unit tested implemented by john
> but the same module is handled by Jonathan for other classes?
> 
> Perhaps some one can show how this is done with Subversion / CVS for
> this team?e

It's the same as in many other languages - including heavily used languages 
such as C and C++. Restricting files such that you're only allowed to have one 
public class in them is something tha only C# and Java do to my knowledge 
(though there are probably other languages out there that do the same). D 
doesn't have that restriction. And even if it did, it's still quite possible 
to have multiple people working on the same file at once. Pretty much any 
modern source control system is set up so that you can have multiple people 
working on the same file at once. If multiple people are making major changes 
at the same time, it can be problematic when they have to merge their changes, 
but it's completely doable and happens often enough in real developement 
enviroments. What D does is completely normal and common. It just doesn't 
match Java and C#.

- Jonathan M Davis