From: Pavel A. on
"Maxim S. Shatskih" wrote:
> Is it really the mechanism of "Checking Dependencies" in MSVC and in BUILD?

For build, it looks so. Build your driver and then check the build.dat file
in the DDK root... all dependencies are there.

VC.2003 seems to save dependencies in .ncb files.

--PA

From: Maxim S. Shatskih on
> Won't this look cool?

Yes, all XML tags can be removed, and the thing will become even better :)

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Anonymous on
> ??? Win32 traditionally used TCHARs, but now, when Win9x is dead, you can
use
> WCHARs the same way. At least it is a good idea to use WCHARs in all
NT-only
> code (server services etc).

No, because win32 VC wizard does not define unicode as a default.

>
> On NT, Unicode is native, and ANSI is compatibility shim.
>
> Non-Unicode NT apps have issues with national languages. For instance,
they
> depend upon the Control Panel settings. Also - the non-Unicode ways of
> supporting Far East are one of the worst things in programming.

Come on, ascii characters always work, stop that nonsense.
Also, I am not bothered about non English characters, if this is the
case, then yes, you need unicode, but why are you thinking in these
arkward ways? And don't forget C and ASCII go together from day
1.


From: Anonymous on
xml is just a whole load of hype


From: Maxim S. Shatskih on
> No, because win32 VC wizard does not define unicode as a default.

Why base your strategy on defaults chosen for beginners to avoid them from
getting lost in lots of notions?

> Come on, ascii characters always work, stop that nonsense.

For Japanese? No ASCII for Japanese, only the ugly DBCS.

> Also, I am not bothered about non English characters

Oh, yes, then sorry, you really do not need Unicode.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com