China DOS Union

Re qzwqzw

"Remember someone once said
It's just a useless tag
Comments are just its side effect"
The explanation about :: has been removed.

"Because when cmd detects an invalid character after a colon, it directly ignores the processing"
Tests show it doesn't matter if the "invalid" character is any character.

"The statement about the opposite number is easy to be misunderstood"
It has been revised. Previously, it was written like this to make it easy for others to understand, but it didn't describe its specific essential function.

"^ is bitwise XOR"
Revised.
btw, I want to ask, what's the difference between XOR and "different"?

It is found in testing that there is no so-called "invalid" character, and it can be any character.
-----------------------
:Of course, any character can follow the colon character
Because the cmd ignores the interpretation of invalid characters

How can we know this?
Define such a label ::errorlabel
Then try to goto ::errorlabel
If it can goto there, it means it is valid
Otherwise, it is invalid

Our comments naturally need to be marked with invalid labels
Otherwise, there may be conflicts with system-defined or our defined labels

The origin of :: actually has a long history
At first, it was because the rem command given by ms-dos could not directly use pipe and redirect symbols
And if you don't echo off, its code will be echoed during runtime
So someone took such a loophole

From these points, it can also be seen
Because there are many fewer preprocessing processes
The efficiency of using :: is higher than that of rem

Later, although many improvements were made to rem in cmd
But :: has spread because it is simple and easy to use and close to the comment mark of high-level languages
----------------------------------

I have never seen the term "bitwise XOR"
"XOR" means different from "OR"
Because the rule of OR is
0|0=0
0|1=1
1|0=1
1|1=1

And XOR is slightly different
0^0=0
0^1=1
1^0=1
1^1=0

[ Last edited by qzwqzw on 2007-5-31 at 12:46 PM ]

Thanks a lot for qzwqzw's clarification..

What I said: The following can be any character, which means that when making comments, all tags that are not called can be used as comments.

Regarding a label like goto ::errorlabel, it can never be reached by goto, so using :: is relatively reasonable.

Personal understanding is that because in goto, if there is a : in the label, then this colon is just a separator. There are several similar ones, such as,, :, (, and the characters after them are not interpreted.
If goto ::errorlabel, then the batch processing will think that it is going to a blank label, and a blank label cannot be constructed and make goto work.

Example: (call is used instead of goto for the sake of being able to return)

@echo off

call :hello;bat

call :hello,vbs

call :hello:asm

call :hello(java

call ::hello

pause&goto :eof



:hello

echo This is one line.

goto :eof

:

echo This is other line.

[ Last edited by lxmxn on 2007-5-31 at 08:15 PM ]

Your understanding of :: is more accurate than mine.
-----------------------------------------------------------------------

Analysis from the perspective of preprocessing

In the preprocessing process of goto and :label,
All special characters are all escaped or filtered.
And goto ::label is preprocessed into a goto empty label label.
The label is ignored by goto.

Because an empty label cannot be set with a jump mark,
So ::label will not work.
-----------------------------------------------------------------------

"Semicolon is an invalid character" is more accurately "Semicolons and other characters are delimiters (or delimiters) used to define tokens".
"The cmd ignores invalid labels" is more accurately "goto ignores the extra parameters after the empty label".

[ Last edited by qzwqzw on 2007-6-2 at 11:51 PM ]

Originally posted by lxmxn at 2007-5-30 22:24:
Re scriptor:

Well, thanks for the supplement, I'll add it in.

According to the explanation by qzwqze on floor 15, the annotation about :: has been removed.

[ Last edited by lxmxn on 2007-5-31 at 10:17 AM ]

Hehe
It's okay!

Floor 15#
It seems I know too little

Ashamed.

DDDDDD

What's missing is it!

Good stuff

Not bad

Collected.

Don't understand much~

%=
① Binary operators in set /a. For example, set /a a"%="b means assigning the remainder of a divided by b to a.
[Add " around %= to prevent % from being escaped, the same below.]
--------------------------------------------------------------------------
The description in [] is incorrect.
In the command line preprocessing of cmd,
The parsing of % occurs earlier than ".
That is, the priority of % is higher than ".
So the quotation marks cannot cancel the escape of %.

Here it should be explained that
It is okay to use a single % in the command line
set /a a%=b

In a batch script, double % need to be used
set /a a%%=b

Okay, collected it.

It would be great to have a post or article that gathers batch processing knowledge like this.

Thanks for sharing, I've bookmarked it!