davidl wrote:
The module package system still stays in the state of the C age. It's
file oriented. I think there's no more sound package system than C# one.
The namespace and distributed packaging is a must nowadays and the
compiler should be project oriented and take project information
be project oriented and take project information
as the compiling base. Also an IDE is quite useful for providing
project templates.
The up side to file based packaging is that the compiler can find the
files without needing extra information. There are several tools that
can build
BCS:
The c# solution works well if you will *only* develop from the IDE but is
a total pain as soon as you need to work with non-language aware tools.
I think Microsoft thinks that an IDE is a part of a modern language. So they
have tried to design a language that almost needs an IDE.
The module package system still stays in the state of the C age. It's file
oriented. I think there's no more sound package system than C# one. The
namespace and distributed packaging is a must nowadays and the compiler
should be project oriented and take project information as the compiling
davidl wrote:
The module package system still stays in the state of the C age. It's
file oriented. I think there's no more sound package system than C# one.
The namespace and distributed packaging is a must nowadays and the
compiler should be project oriented and take project information
