I hoped to avoid the dependencies in std.c.stdio by using std.stdio, but suddenly, out of nowhere, a public import creates a conflict.

Lars Ivar Igesund

Lars Ivar Igesund wrote:
> I hoped to avoid the dependencies in std.c.stdio by using std.stdio, but suddenly, out of nowhere, a public import creates a conflict.
> 
> Lars Ivar Igesund

It is documented "std.c.stdio is automatically imported when importing std.stdio." on http://www.digitalmars.com/d/phobos.html#stdio, but I don't understand why?

Walter, why make it impossible for us to only import what we want by drawing everything else in with "public import"? Help!

-- 
Justin (a/k/a jcc7)
http://jcc_7.tripod.com/d/