China DOS Union

Originally posted by namejm at 2007-4-9 08:57 AM:
　　1、
　　From your other replies, it can be seen that you are someone involved in programming, but saying such a thing is quite surprising. Let's ask: In an object-oriented high-level language, if you don't provide an object...

Oh, because you violated a characteristic of batch processing, which is simplicity and speed..

And adding parameters is exactly for such a purpose. Otherwise, I might as well use xcopy which is simpler.

After adding parameters, we can use

batch.cmd ……

In this way, the workload can be saved. The purpose of making batch processing is: to make work more efficient instead of more troublesome, which is why I have this statement.

Initially, I originally planned to propose using an.ini file.

Think about it, the first time we use it is for fun. The second time we use it is because the novelty hasn't worn off yet. Then for the nth time we use it, what reason do we have to trouble ourselves like this?

So, now as long as I am writing batch processing at the practical level, I all add parameters.

That's why this statement exists.

4、


Quote:
As for illegal characters, it is also very easy to defend. Write a subroutine.
Using code like %data:~0,1% can do the trick.



　　Regarding the defense of illegal characters, it doesn't seem as simple as you said. For specific reasons, please refer to the analysis by willsort on floor 13 of this thread.

As for the source file, there is no need for us to complete these judgments in the batch processing.

Because Microsoft has considered these parameters at the beginning of design.

All we need to do is capture this kind of error.

Re flyinspace 『Post 106』and 『Post 107』:

　　I originally thought you meant that if you don't write so many parameters in the code, then this script is just a piece of junk. But from your two replies, I realized you meant you hope to be able to add parameters when calling the script. It seems I misunderstood.

　　But the calling format of batch.cmd [source file] [target file] [switch] requires learning more parameters, and lazy novices like me will definitely be daunted. Using parameters is convenient for programmers, but a torture for ordinary users. So the original intention of me writing this script is: let users follow the prompts step by step, foolproof operation——I think no backup fanatic will use this script to back up files frequently several times a day? If there are a large number of backup operations or high backup requirements, it is recommended to use a dedicated backup program written in a high-level language, and this script is not recommended. Therefore, the positioning of this script determines its operation method.

　　Because this script provides both manual input and mouse drag-and-drop methods. For the drag-and-drop method, there is no need to detect special characters at all, which I admit. But with manual input, it's difficult to ensure that users won't input special characters. For example, if redirect symbols are used in some places, it is very likely to overwrite important files; to be safe, it is necessary to detect special characters.

Actually, it's not necessary that every bat has to carry parameters.

Originally posted by willsort at 2006-5-24 02:47:
Re namejm:
The following statements can remove the possible quotes in the path, convert the relative path to the absolute path, convert the non-standard path to the standard path (C:\\-->C:\), and judge whether the path effectively exists and whether it is the root path. However, it still cannot resist the illegal characters (>|) in the path. I wonder if other brothers have any better ways?

　　This problem has troubled me for a long time. I just found a relatively perfect solution now, that is: create a random folder in the %tmp% directory and leave the task of judging illegal characters to the operating system. However, what makes me a little unhappy is that this solution produces temporary files that I have always tried to avoid.

　　For the specific code, please refer to this post: Batch processing to judge whether the input file name is legal

Good stuff, give it a support

Dare not even dare to look ^_^