comment on

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.

In reply to Re^2: Any (Active)perl influence on PowerShell? by mr_mischief
in thread Any (Active)perl influence on PowerShell? by sg

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks