import syntax

[Karl Bochert]

Is there some reason why the syntax is 
import std.c.stdio
Rather than 
import std\c\stdio

The dot syntax prevents the use of relative paths to modules ( I'm guessing -- I
haven't actually tried 'import ......foo;' )

Are relative paths considered bad for imports?
Is this just an unfortunate side-effect of a syntax that has other advantages?

I guess the work-around is to use the -I compiler switch which seems like a
terrible approach to me, moving information that should be in the source to the
makefile.