"J Anderson" <REMOVEanderson@badmama.com.au> wrote in message news:bu4ne6$2t0a$1@digitaldaemon.com...
> J C Calvarese wrote:
>
> > J Anderson wrote:
> >
> >> Walter wrote:
> >>
> >>> "imr1984" <imr1984_member@pathlink.com> wrote in message
> >>>> If so why cant they be put into the windows.d import file?
> >>>
> >>>
> >>> I want to keep windows.d an analogue of windows.h
> >>>
> >>>
> >> Why no have a dwindows (or something), which imports all the related
> >> stuff for windows?
> >>
> >
> > Are you thinking of something like this?
> >
> > // ----------------------------------- //
> >
> > module std.windows.windows;
> >
> >
> > extern (C) void gc_init();
> > extern (C) void gc_term();
> > extern (C) void _minit();
> > extern (C) void _moduleCtor();
> > extern (C) void _moduleUnitTests();
> >
> > // ----------------------------------- //
> >
> >
> > Seems like a good idea to me.  I like to keep the mysterious stuff underneath the hood.  I prefer one line with "import std.windows.windows;" to five cryptic lines that make it easy for me to mess up something.
> >
> >
> Exactly. Or parhaps.
>
> module std.d.windows;
>
> import std.c.windows;
>
> extern (C) void gc_init();
> extern (C) void gc_term();
> extern (C) void _minit();
> extern (C) void _moduleCtor();
> extern (C) void _moduleUnitTests();

Why has nobody suggested:

extern (C)
{
    void gc_init();
    void gc_term();
    void _minit();
    void _moduleCtor();
    void _moduleUnitTests();
}

?

It seems C should allow something like this:

void gc_init(), gc_term(), _minit(), _moduleCtor(),_moduleUnitTests();

But I don't think it does.

?

Sean