• Matthew (1/1) Mar 10 2005 Title says it all.
• Jarrett Billingsley (2/3) Mar 10 2005 Doesn't writef/writefln accept wchar[] / dchar[] as format strings? Or ...
• Matthew (6/9) Mar 10 2005 Sure. Or at least, I expect so.
• Ben Hinkle (7/8) Mar 10 2005 I think it's a bug. It is commented out in std.c.stdio - it shouldn't be...
• Sean Kelly (6/6) Mar 11 2005 I think it was an accident. If you're so inclined, however, you might w...

"Matthew" <admin.hat stlsoft.dot.org> writes:

Title says it all.

"Jarrett Billingsley" <kb3ctd2 yahoo.com> writes:

 Title says it all.

Doesn't writef/writefln accept wchar[] / dchar[] as format strings?  Or is 
there some other functionality that's missing? 

"Matthew" <admin stlsoft.dot.dot.dot.dot.org> writes:

"Jarrett Billingsley" <kb3ctd2 yahoo.com> wrote in message 
news:d0qdln$1cs$1 digitaldaemon.com...
 Title says it all.

 Doesn't writef/writefln accept wchar[] / dchar[] as format strings? 
 Or is there some other functionality that's missing?

Sure. Or at least, I expect so.

I just got back to some old code from last year, for turning COM type 
libraries into classes, and it's got a lot of wprintf() in it, which now 
no longer compiles. So it just prompted my curiosity. 

"Ben Hinkle" <ben.hinkle gmail.com> writes:

"Matthew" <admin.hat stlsoft.dot.org> wrote in message 
news:d0p819$1rme$1 digitaldaemon.com...
 Title says it all.

I think it's a bug. It is commented out in std.c.stdio - it shouldn't be.
The history is that it was in object.d but declared as taking wchar which 
was the wrong type on Linux. In order to make it take wchar_t it was removed 
from object.d but it looks like it wasn't uncommented in std.c.stdio.

-Ben 

Sean Kelly <sean f4.ca> writes:

I think it was an accident.  If you're so inclined, however, you might want to
take a look at my standard C headers:

http://home.f4.ca/sean/d/stdc.zip

They're a bit more complete than the ones in Phobos, and the layout is as close
to standard as I could get it without any undue cleverness.


Sean