"Antti Sykäri" <jsykari@cc.hut.fi> wrote in message news:akh33p$iff$1@digitaldaemon.com...
> How about passing the arguments between modules that are compiled separately? Is the calling convention documented in the object file, perhaps? Or maybe it is derivable from the function's signature?

It's really up to the compiler system. A D implementation doesn't even require .obj files, it can generate an executable directly. The current implementation, however, adheres to the boring, traditional .obj file method - but it doesn't have to be that way.

"Pavel Minayev" <evilone@omen.ru> wrote in message news:CFN37495671212963@news.digitalmars.com...
> Yes, exactly. Lots of times I want to break out of the loop conditionally, using switch-statement - but arrgh! goto only...

There is the
    break label;
syntax, useful for breaking out of arbitrarilly nested loops.

"Matthew Wilson" <matthew@thedjournal.com> wrote in message news:al1end$2d9f$1@digitaldaemon.com...
> I can remember the first time I realised (in a happiling compiling
program)
> that Java does not have out-parameters. To say I was disgusted would be putting it mildly ...

The workaround for lack of out parameters in Java is awful. To my mind it's the most serious shortcoming of the language.

At one time, I intended to use the 'if' for conditional compilation. It turned out to be too confusing - the version statement/declaration works much better.

So far, I've got the D templates about 1/3 working. Syntax analysis, argument deduction, and partial specialization are implemented. Next comes instantiation, followed by object code generation.

If we drop the fall-through feature we should change the entire sintax of
the switch statement.
For example:

int blah = rand();

switch(blah)
case(1)
    return;
case(2)
{
    goto case(3);
}
case(3) case(4)
    goto default;
default
{/*do nothing*/}

This way the compiler will fail if trying to compile old C code, and the programmer will known that something should be modified.

If we don't change the sintax the following code won't work as expected:

switch(1)
{
    case 1: case 2:
    printf("GOOD");
    default:
    printf("BAD");
}

Just some thoughts. Anyway I agree that the language should prevent errors from happening.