This includes the new library layout. It's a bit of a nuisance to update source code, but the good news is the compiler error messages will help out a lot. Also, there's /dmd/bin/replace.exe, which is a handy tool for global search and replace. Use it like:

    replace *.d
    String to be replaced (80 characters max)?
    import c.stdio
    Replacement string?
    import std.c.stdio

etc. which should make short work of most of it.


http://www.digitalmars.com/d/changelog.html

From the docs:

    std.c.windows.linux

??

Lars Ivar Igesund

"Walter" <walter@digitalmars.com> wrote in message news:boa8ki$1g9u$1@digitaldaemon.com...
> This includes the new library layout. It's a bit of a nuisance to update source code, but the good news is the compiler error messages will help
out
> a lot. Also, there's /dmd/bin/replace.exe, which is a handy tool for
global
> search and replace. Use it like:
>
>     replace *.d
>     String to be replaced (80 characters max)?
>     import c.stdio
>     Replacement string?
>     import std.c.stdio
>
> etc. which should make short work of most of it.
>
>
> http://www.digitalmars.com/d/changelog.html
>
>

"Lars Ivar Igesund" <larsivi@stud.ntnu.no> wrote in message news:boa9sp$1i2u$1@digitaldaemon.com...
> From the docs:
>
>     std.c.windows.linux
>
> ??
>
> Lars Ivar Igesund

Typo. Should be std.c.linux

Walter wrote:

> Typo. Should be std.c.linux

I asked this on the wiki but no answer still, so I'm sorry for intruding...

I'm qurious, why std.c.linux? Shouldn't it be std.c.unix? Or std.c.posix? There aren't very much linux-specific stuff in there is it?

Elias

It's glad for me that almost "import" were set to "private". Why are these "public" still ?

random.d:
import std.c.linux.linux;

thread.d
import std.c.windows.windows;

YT

In article <boa8ki$1g9u$1@digitaldaemon.com>, Walter says...
>
>This includes the new library layout.

yuck, you didn't go far enough, "we" kind expected
that when you said the python lib would be a good model...
changes are irrelevant! basically no structure changes
just naming...
I'm not sure this is going to help to promote submissions
by independent volunteer contributions... a missed opportunity.

<joke> well, what could we expected from a guy that
calls "this" to ctor?</joke> :)

>It's a bit of a nuisance to update
>source code, but the good news is the compiler error messages will help out
>a lot. Also, there's /dmd/bin/replace.exe, which is a handy tool for global
>search and replace. Use it like:
>
>    replace *.d
>    String to be replaced (80 characters max)?
>    import c.stdio
>    Replacement string?
>    import std.c.stdio
>
Can this be put into a batch/shell file with all the import changes?
like:
replace *.d "import c.stdio" "import std.c.stdio"
replace *.d "import path" "import std.path"

if somebody started that and post it here others could add to it and soon we would have a conversion tool.

Ant

In article <boapcb$28cj$1@digitaldaemon.com>, Elias Martenson says...

>
>I'm qurious, why std.c.linux? Shouldn't it be std.c.unix? Or std.c.posix? There aren't very much linux-specific stuff in there is it?

I had the same thought myself. I guess because Walter only supports two
platforms:
x86 Win32
x86 Linux

Probably should have been std.c.unix for UNIX/POSIX stuff and std.c.unix.linux for Linux only specific stuff (if any).  I don't think Walter uses any other UNIX besides Linux so he may not feel comfortable in this area.

"Elias Martenson" <elias-m@algonet.se> wrote in message news:boapcb$28cj$1@digitaldaemon.com...
> I asked this on the wiki but no answer still, so I'm sorry for
intruding...

You're not intruding. Ask away!

> I'm qurious, why std.c.linux? Shouldn't it be std.c.unix? Or std.c.posix? There aren't very much linux-specific stuff in there is it?

Good question. The answer is that there are several different families of unix, of which linux is one. There's BSD unix, SCO unix, etc. When D is implemented on them, I can see an std.c.bsdunix, etc., being made for it. I don't see a problem with the likelihood of the bsdunix and linux files being 90% the same.

"Y.Tomino" <demoonlit@inter7.jp> wrote in message news:boar82$2auv$1@digitaldaemon.com...
> It's glad for me that almost "import" were set to "private". Why are these "public" still ?
>
> random.d:
> import std.c.linux.linux;
>
> thread.d
> import std.c.windows.windows;
>
> YT

Sloth on my part. They should be private.

Walter wrote:
> This includes the new library layout. It's a bit of a nuisance to update
> source code, but the good news is the compiler error messages will help out
> a lot. ...
> 

I've been trying to get DIG (Carlos's modified version of 0.0.14) to compile with the new phobos structure in DMD 0.75, so I've gone through and changed all the phobos imports that I could find.

Some of the error message seem to indicate there might be some small problems with phobos.  (But I may just be clueless.)  In any case, these changes seemed to help my situation, so I'm submitting them for your consideration:

phobos\internal\gc\gc.d (change line 16):
import internal.gc.gcx;

phobos\internal\gc\gcx.d (change line 33):
import internal.gc.gcbits;

phobos\std\gcx.d (change line 40):
   import internal.gc.win32;

phobos\internal\gc\gcbits.d (inserted line at top):
module internal.gc.gcbits;

phobos\std\intrinsic.d (change line 11):
module std.intrinsic;  /+ was std.math! +/

phobos\std\c\windows\windows.d (inserted line at top):
module std.c.windows.windows;

phobos\std\ctype.d (inserted line at top):
module std.ctype;

phobos\std\windows\syserror.d (inserted line at top):
module std.windows.syserror;



My latest error message is:
net\BurtonRadons\dig\windows\frame.d(9): module gc is in multiple packages std.gc

where the offending line is:
private import std.gc;

If I change it to:
private import internal.gc.gc;

My new error message is:
net\BurtonRadons\dig\windows\base.d(7): import std conflicts with windows.std at net\BurtonRadons\dig\windows\windows.d(7)

net\BurtonRadons\dig\windows\windows.d(7):
import std.c.windows.windows;

net\BurtonRadons\dig\windows\base.d(7):
import std.ctype;

I'm running around in circles at this point (I don't even know what direction I should be going).  Any ideas, hints, tips, pointers, etc. would be must appreciated.


Justin
http://jcc_7.tripod.com/d/