Greetings:
D looks like a great language, better even than C#.
Congratulations!
-----
In fact I suggest two standalone tools;
one to HTMLify the code, and one to
extract the code from the HTML. The
user would write the code as usual and then
HTMLify it to form the
documentation, as silly as that documentation would
be.
-----
I would agree that D code should be in D syntax, if you want html write a
tool to either convert or strip.
I prefer C's requirement that all declarations in a statement block
appear
before any executable code. Allowing the mixing of declarations and
executable
may make it difficult to find a declaration, which is poor
programming style.
I do however like the ability to declare the
iterator of a for statement within
the statement (which C# does as
well).
-----
C++, C# and Java allow you to declare a variable
anywhere not just at the beging of a scope
in C it is valid to write
void func( int i ) {
printf("i is %d\n", i);
{
int
j = i+5;
printf("j is
%d\n", j);
}
}
not too far removed from
void func( int i ) {
printf("i is %d\n", i);
int j
= i+5;
}
With
C++, separate files for the methods can still be done because of
the
class::func() { ... } syntax. This seems to be impossible with D (and
C#); that
the methods must be fully declared inside the class (yuck!). I can
see why C#
needs to do that, but why does D? Is it simply because you don't
like
prototypes?
-----
all I can say is how bigs you project and how much
effort do you have to put in to keep the headers inline with the implementations
(and why write them twice).
get an editor that does code folding,
the benifits of having implementation and interface
defined together outweighs the slightly larger files (imho) ( yes I have been
know to write 3 sub classes in 3 separate modules just to keep the code
separated but still prefer it as it is).
I do prefer the Java one public class per file
, and would like D to allow a class per file or a module per file.