Hauke Duden wrote:

> Yan wrote:
[...]
>> but with logical structure.
> Agreed!

But how is the logical structure related to the physical layout of a project?

From the friends section of the docs:
| It makes sense that tightly related classes should be in the same module

Should this be exended to the already available meaning of `package', i.e. modules that reside in the same directory?

So long.

In article <c0bmap$2lsi$2@digitaldaemon.com>, Manfred Nowak says...
>
>Hauke Duden wrote:
>
>> Yan wrote:
>[...]
>>> but with logical structure.
>> Agreed!
>
>But how is the logical structure related to the physical layout of a project?

IMHO logical structure should not be related to the physical layout.
"project" is a substance controlled by IDE (for example) but not by compiler or
linker..
Classes of the same module could be placed in several files (even
on different computers..)
Relation of logical structure and physical layout should be
determined by programmer when he call compiler,linker or make..
May be i'm wrong but i see this concept as more universal.
regards
Yan

>
>From the friends section of the docs:
>| It makes sense that tightly related classes should be in the same module
>
>Should this be exended to the already available meaning of `package', i.e. modules that reside in the same directory?
>
>So long.

Yan wrote:

[...]
> "project" is a substance controlled by IDE (for example) but not by
> compiler
[...]
> Classes of the same module could be placed in several files (even on
> different computers..)

What are the differences between your thinking in modules and projekts? And why s it not neccassary, that the used formal language is aware of that?

So long.