Mac OSX installer for dmd

Leandro Lucarella luca at llucax.com.ar
Mon Aug 2 21:13:19 PDT 2010


dsimcha, el  3 de agosto a las 02:16 me escribiste:
> == Quote from Leandro Lucarella (luca at llucax.com.ar)'s article
> > With this default, I think complaining when no symbol from an imported
> > module is used would be better to avoid extra unneeded dependencies. But
> > I suggested that before and you don't like it.
> > Too bad.
> 
> But then you wouldn't be able to do import somelib.all;

If a syntax like import somelib.*; would be implemented, that kind of
"import all" statements could be taken as a special case and don't
trigger the error. public imports should not trigger errors either,
because you are just explicitly propagating what's in a module.

> because importing all the modules you need individually is tedious, annoying
> boilerplate code.  IMHO in a modern language with good metaprogramming facilities
> like D, boilerplate code should absolutely, 110%, at all costs, be swept off to
> the ash heap of history.  It's boring to write, hard to maintain (in the sense
> that it's just more code to slog through) and encourages cut-and-paste style
> coding.  I refuse to write even the few lines of boilerplate it takes to import
> the same 15 modules over and over, when I can have a module that just publicly
> imports all of the ones I typically need.

Again, I completely agree. But you can avoid all the boilerplate code
and keep the dependencies explicit by default. They are not mutually
exclusive goals.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Y será el día en que la electricidad deje de ser rayo y sea depilador
femenino.
	-- Ricardo Vaporeso


More information about the Digitalmars-d mailing list