Lots of Unix tools have a flag that means to only report what would be changed. It's certainly not a first.
It's not exactly the same, but I usually do run find(1) with a -print action before I use an -exec action, for one.
The idea of having a standard object structure among all the cmdlets and having it fall back to text is what I'd consider the biggest win, followed by having the system actually used by other tools within the Windows system.
There have been many tools for Windows that could have been the basis for such a standardized approach, but it's good to know they have an interest in making proper system out of it. WSH and VBScript or some random collection of COM objects would not have been as nice.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.