Thread replies: 12
Thread images: 2
Thread images: 2
File: nt31logocut.png (4KB, 355x425px) Image search:
[Google]
4KB, 355x425px
>The time a batch script takes to execute is at least O(n*(n-1)/2) (aka O(n^2)) in the LENGTH OF THE FILE, INCLUDING COMMENTS. The reason is that the batch engine reads the entire file, then executes a line, then reads the file again, then executes another line, and so on.
>It is therefore customary to use a GOTO to skip over sizable comment blocks, so that you don’t have to “execute” them.
Good job Microsoft
>>
it is to make sure no bug is included.
us government still uses 3.1.
>>
>>55042901
This still applies to Windows 10
>>
>>55042881
I can forgive Microsoft for this because in Windows 10, the cmd.exe window is now resizable.
>>
File: latest.jpg (212KB, 544x408px) Image search:
[Google]
212KB, 544x408px
>>55043714
>>
>>55043714
It's always been resizable, genius.
>>
>>55044057
Uhh, no it hasn't. You could only resize it vertically. Horizontal size had to be configured somewhere in the Options window, which was a stupid pain in the ass.
In Windows 10, you can finally resize it any way imaginable, just like any other sane terminal allows you to.
>>
We cheated on the old days by using :: as a rem statement
>>
>tfw microsoft still uses batch scripts like razzle.cmd to compile windows
>>
>>55044078
>it's not resizable except when it is
>>
Why did they create BATCH instead of some dialect of BASIC considering Microsoft's history with that?
>>
>>55044846
>tfw compiling Windows is black magic that even Microsoft doesn't understand
Thread posts: 12
Thread images: 2
Thread images: 2