On Saturday, November 01, 2014 18:57:09 H. S. Teoh via Digitalmars-d wrote:
Jonathan was also reportedly working on breaking up std.datetime into
manageable pieces, but it's been a long time and so far it seems to have
been far easier said than done.
Breaking it up isn't all that hard, just
The module declaration, and the name and path of D files do not
need to match each other. You include a D file while compiling
the project, and module declarations are cared only.
Based on above behaviour of design, allowing only one module
keyword, and that is on top of D code file seems
tcak:
Is there any VERY SPECIAL reason behind that limitation?
What advantages gives removing that limitation? Is the price in
increased complexity worth paying?
Bye,
bearophile
On Sat, 01 Nov 2014 09:24:46 +
bearophile via Digitalmars-d digitalmars-d@puremagic.com wrote:
tcak:
Is there any VERY SPECIAL reason behind that limitation?
What advantages gives removing that limitation? Is the price in
increased complexity worth paying?
nested modules, like in
Am 01.11.2014 um 10:29 schrieb ketmar via Digitalmars-d:
On Sat, 01 Nov 2014 09:24:46 +
bearophile via Digitalmars-d digitalmars-d@puremagic.com wrote:
tcak:
Is there any VERY SPECIAL reason behind that limitation?
What advantages gives removing that limitation? Is the price in
On Sat, 01 Nov 2014 11:04:32 +0100
Paulo Pinto via Digitalmars-d digitalmars-d@puremagic.com wrote:
Am 01.11.2014 um 10:29 schrieb ketmar via Digitalmars-d:
On Sat, 01 Nov 2014 09:24:46 +
bearophile via Digitalmars-d digitalmars-d@puremagic.com wrote:
tcak:
Is there any VERY
On Saturday, November 01, 2014 07:52:38 tcak via Digitalmars-d wrote:
The module declaration, and the name and path of D files do not
need to match each other. You include a D file while compiling
the project, and module declarations are cared only.
Based on above behaviour of design,
On Saturday, 1 November 2014 at 10:04:23 UTC, Paulo Pinto wrote:
Am 01.11.2014 um 10:29 schrieb ketmar via Digitalmars-d:
A few languages have nested packages. Quite usefull for
implementation packages.
Beware of Wirth's quest for simplicity, even Go is a quite
powerful in regards to
On Sat, 01 Nov 2014 13:04:57 +
tcak via Digitalmars-d digitalmars-d@puremagic.com wrote:
My biggest concern is that just to collect similar things
together (mostly small things), I have to create another new file
which makes me feel grrr.
if they are so similar, put them in one module.
On Saturday, 1 November 2014 at 13:04:58 UTC, tcak wrote:
My biggest concern is that just to collect similar things
together (mostly small things), I have to create another new
file
which makes me feel grrr.
I am afraid you need to get used to it because it is fundamental
design
On Saturday, 1 November 2014 at 10:32:48 UTC, Jonathan M Davis
via Digitalmars-d wrote:
On Saturday, November 01, 2014 07:52:38 tcak via Digitalmars-d
wrote:
The module declaration, and the name and path of D files do
not
need to match each other. You include a D file while compiling
the
On Sat, 01 Nov 2014 14:03:50 +
Nicolas Sicard via Digitalmars-d digitalmars-d@puremagic.com wrote:
What's the reason why the module keyword was introduced in the
first place? The package and module hierarchy could have been
deduced from the directory and file hierarchy, as it is the case
On Saturday, 1 November 2014 at 07:52:39 UTC, tcak wrote:
The module declaration, and the name and path of D files do
not need to match each other. You include a D file while
compiling the project, and module declarations are cared only.
Based on above behaviour of design, allowing only one
On Saturday, 1 November 2014 at 14:03:51 UTC, Nicolas Sicard
wrote:
What's the reason why the module keyword was introduced in the
first place? The package and module hierarchy could have been
deduced from the directory and file hierarchy, as it is the
case in Python, IIRC. The search rules
On Saturday, 1 November 2014 at 14:18:53 UTC, Mike wrote:
I find this, and the fact that packages and modules map
directly to directories and files, to be an arbitrary
limitation as well.
It is not necessary but it results in elegant mapping. I wish it
pushed harder for module == namespace
On Saturday, 1 November 2014 at 14:40:16 UTC, Dicebot wrote:
On Saturday, 1 November 2014 at 14:03:51 UTC, Nicolas Sicard
wrote:
What's the reason why the module keyword was introduced in the
first place? The package and module hierarchy could have been
deduced from the directory and file
On Saturday, 1 November 2014 at 14:48:33 UTC, Nicolas Sicard
wrote:
On Saturday, 1 November 2014 at 14:40:16 UTC, Dicebot wrote:
On Saturday, 1 November 2014 at 14:03:51 UTC, Nicolas Sicard
wrote:
What's the reason why the module keyword was introduced in
the first place? The package and
On Saturday, 1 November 2014 at 15:32:22 UTC, Dicebot wrote:
On Saturday, 1 November 2014 at 14:48:33 UTC, Nicolas Sicard
wrote:
On Saturday, 1 November 2014 at 14:40:16 UTC, Dicebot wrote:
On Saturday, 1 November 2014 at 14:03:51 UTC, Nicolas Sicard
wrote:
What's the reason why the module
bearophile wrote in message news:aghnzoieibfgivzxa...@forum.dlang.org...
What advantages gives removing that limitation?
Multi-module single-file test cases!
Is the price in increased complexity worth paying?
I doubt it.
On 11/1/2014 6:31 AM, Dicebot wrote:
I am afraid you need to get used to it because it is fundamental design decision
of D module system and quite a feature on its own. Lot of files == awesome.
Cramming lots of code into one source file made abundant sense on floppy disk
systems, because
On 11/1/2014 7:40 AM, Dicebot wrote:
I see no reason to put module declarations in single level projects with no
packages.
Sometimes it can be handy to have a module name different from a file name,
especially when trying to track down a bug, but this is rare.
On Sat, Nov 01, 2014 at 03:23:17PM -0700, Walter Bright via Digitalmars-d wrote:
On 11/1/2014 6:31 AM, Dicebot wrote:
I am afraid you need to get used to it because it is fundamental
design decision of D module system and quite a feature on its own.
Lot of files == awesome.
Cramming lots of
On Sunday, 2 November 2014 at 01:59:10 UTC, H. S. Teoh via
Digitalmars-d wrote:
I've tried on one or two occasions to split std.algorithm into
more
manageable submodules. Unfortunately, it's not a trivial task
due to
over-reliance on module-global imports.
I've proposed an enhancement to
23 matches
Mail list logo
