[<<]Message[>>]    [<<]Author[>>]        Subject        [<<]Thread    

Number   :  2827
Date     :  2002-09-20
Author   :  Kan Yabumoto
Subject  :  If it ain't ...
Size(KB) :  1


Ed:

Thank you for your bug report.

In this case, /OX defaults to /OX3 which should still
work (and therefore a practical work-around here).

They say "If it ain't broke, don't fix it."
Furthermore, "If it ain't broke, don't break it."
But, "If it ain't fixed, it's still broken."

When we added the support for the optional separator
between the switch alphabet(s) and parameter (colon),
we cleaned up the section of XXCOPY source code which
is responsible in parsing the command line.

The process was pretty straight forward, but, it was
a huge editing job (due to the large number of switches
and associated parsing irregularities). So, a few cases
did not preserve the exactly the same behavior.

Also, the funny thing is the error message contains
extra characters (the next switches in the line are
also shown). We will also look into that...

Regardless of the sorry inconveniences that are caused
by this kind of incidents, we don't shy away from
making XXCOPY better. Else, you will have a mediocre
product. Cleaning up ugly coding is a necessary
step before adding a useful feature. That's how we
look at the situation.

Our motto is,

"If it ain't cool, let's make it cool."

Kan Yabumoto
=======================================================
At 2002-09-20 04:39, you wrote:
>Hi, Kan.
>
>I downloaded 2.82.4 but it gave me some trouble.
>
>xxcopy c:\ %1\ /clone /EX"C:\DOS\BATS\_CLONENOT.TXT"
> /OA"C:\xxcopylog.txt" /OX /yy
>
>2.56.3
>no problem
>
>2.82.4
>"Invalid switch (/OX /yy)"



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.