[nem-en] loving Nemerle

[d]

On Thu, Oct 27, 2005 at 06:42:53PM +0200, Kamil Skalski wrote:

> Well, I think that it would be a little bit too limiting for users...
> Especially, that the question remains which style do we want to
> enforce... In fact currently we have a small piece of such validation,
> with -pedantic-lexer option compiler warns about usage of tabs in
> sources, so maybe it's not that bad idea.
> Maybe the way to do this elegantly would be to develop a separate
> tool, which would use Nemerle.Compiler.dll library and provide it's
> own "validating lexer / parser" pipelines, which would just parse all
> sources in the project and show the places where style / formatting
> issues are found (according to specified rules). I don't need such
> tool myself, but if anyone does, it shouldn't be that hard to develop
> (feel free to ask about hints).

 This would be great. Actually IMO such a thing should be enabled by 
default. The more the compiler cares about, the better. If some of the 
work can be taken care of by the machine, let's shift the burden to it!
 This issue is similar in philosophy to static typing - sure the 
programmer can take care of types themself, but people make mistakes 
and if those can be detected by the compiler, it only makes for better 
code and time savings. Why not employ this strategy in the case of coding
conventions, which are actually *very* important (at least to the human 
part of the software creation process).
 IMO it would be a good idea to make it ncc's deafault behaviour, to 
check that the programmer sticks to a certain style/formatting 
convention. He would be able to provide an explicit style description, 
use a "predefined" style (such as ncc-style for example) or perhaps 
it could be detected "on the fly" and consistency checked in the rest
of the source code.
 You say, that this would be limiting.. The option could always be 
disabled, but I think, it's use should be encouraged. Developers 
could then accept only "validated" code from others (anyone in the case
of open-source, or their employees in a work setting). 
 I totally believe the programmer should be restricted to doing only what
they are supposed to. And the more can be forced on compiler level, the
better.

d

-- 
https://hell.art.pl == terror.org.pl == terror.icm.edu.pl/~d/gpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /mailman/pipermail/devel-en/attachments/20051027/4f139cea/attachment.bin