forward slash vs backward slash on ordinary (non-MSYS, non-Cygwin) windows commandline

[vedaal at nym.hush.com]

MFPA and Mika wrote that an option to know how many keys there are 
on a keyring would be to use:

gpg --export -a|gpg --import

and Rob suggested (for linux systems) :
gpg2 --list-keys|grep "^pub"|wc -l

Both of these work on windows using either the Cygwin or MSys 
commandlines,

but for the ordinary windows dos box, which doesn't allow pipes,
the following works:

gpg --import c:/gnupg/pubring.gpg

(assuming that the keyring is in the c:\gnupg\home directory)

BUT

it works ONLY if the forward slash is used.

If the backward slash is used, then gnupg gives an error that it 
can't find the directory.

Here is the gnupg output

gpg --import C:\gnupg\home\pubring.gpg
gpg: can't open `C:gnupg\pubring.gpg': No such file or directory
gpg: Total number processed: 0

Under what circumstances does gnupg on windows, require the forward 
slash?

(not a big deal,
as gnupg does give an error message that the directory can't be 
found,
and that can be taken as an indication to use a forward slash 
rather than a backward slash)

maybe  this could be added to the documentation or the FAQ ?


vedaal